Re: giving up on 1 buffers error messsage

From: Andriy Tkachuk (andrit_at_ukr.net)
Date: 02/25/05

  • Next message: Peter Jeremy: "Re: Driver Update Disk discussion"
    To: <freebsd-hackers@freebsd.org>
    Date: Fri, 25 Feb 2005 13:46:30 +0530
    
    

    It is interesting why threre is no answer for this question so long time,
    regardless that it was posted 2 times :)

    For me it is also interesting to get the answer for this question
    since from time to time i also confused by such msgs on
    shutdown.

    >
    > syncing disks... 54 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 giving up on 1
    > buffers
    >
    >
    > Hi,
    >
    > I am referring to the message when the code in kern_shutdown.c in bsd
    > 4.10 is called at the time of boot() system call
    >
    > My understanding is that this message tells us that 1 buffer from the
    > buffer cache was not successfully flushed to disk, since the last call to
    > sync(). Is that right? In that case what happens to this buffer? Is it
    > discarded and assume that fsck will fix this on reboot?
    >
    > Since the syncer process runs periodically, can this error message be
    > avoided if we wait long enough to guarantee flushing to disk (I have tried
    > with DELAYS upto 30 seconds but I still get the error sometimes).
    >
    > I am actually trying to use this same code at a different point in time
    > (not during shutdown, but to take a checkpoint), so I am not sure if that
    > contributes to this error message?
    >
    >
    >
    >
    > _______________________________________________
    > freebsd-hackers@freebsd.org mailing list
    > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
    > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"
    >
    >

    _______________________________________________
    freebsd-hackers@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
    To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"


  • Next message: Peter Jeremy: "Re: Driver Update Disk discussion"

    Relevant Pages

    • Re: why the usage of gets() is dangerous.
      ... that is to say one that always terminates the program ... with an error message if the buffer is exceeded. ... You have to make it safe within the guarantees provided by the C ...
      (comp.lang.c)
    • [Full-disclosure] Re: Buffer-overflow in Ultr@VNC 1.0.1 viewer and server
      ... overflow the buffer in 3 bytes? ... the buffer is overflowed just by those 3 bytes plus the Windows ... error message created with FormatMessage. ... Limited just because the attacker has no control for executing malicious ...
      (Full-Disclosure)
    • Re: Buffer-overflow in Ultr@VNC 1.0.1 viewer and server
      ... overflow the buffer in 3 bytes? ... the buffer is overflowed just by those 3 bytes plus the Windows ... error message created with FormatMessage. ... Limited just because the attacker has no control for executing malicious ...
      (Bugtraq)
    • Re: giving up on 1 buffers error messsage
      ... The disk write procedures should wait for the disk to be ready, ... If, for some reason, a disk device does not empty its buffer after some ... Note that sync will not solve the problem. ... >>Since the syncer process runs periodically, can this error message be ...
      (freebsd-hackers)
    • Re: Texturing fails silently, objects are all white
      ... in 16-bit mode so multiplied by 2 to account for a back buffer, ... I would like where necessary to downsample, or output an error message ... >> couldn't find any way to detect failure. ... Should I used the default pool ...
      (microsoft.public.win32.programmer.directx.graphics)