Re: giving up on 1 buffers error messsage

From: João Carlos Mendes Luís (jonny_at_jonny.eng.br)
Date: 02/25/05

  • Next message: Eric Kjeldergaard: "Re: sched_4bsd.c Quantum change"
    Date: Fri, 25 Feb 2005 10:36:20 -0300
    To: Andriy Tkachuk <andrit@ukr.net>
    
    

    Although I am not exactly an expert on the field, I'll try to explain.

    The disk write procedures should wait for the disk to be ready, and this
    involves (soft)interrupts. When rebooting, the system can only wait for
    the device drivers to empty the write buffers, since it is not in
    interrupt context.

    If, for some reason, a disk device does not empty its buffer after some
    time, you will receive this "give up" message. In your case, one last
    buffer did not get to its destination, but 53 did.

    I get this message mostly on hard disk failures or panics related to
    disk devices.

    Note that sync will not solve the problem. What sync does is exactly
    what the reboot is doing: asks the system to empty its buffers. The
    only difference is that sync() does not wait for return. Indeed, this
    was the behaviour on pre-softupdate ages, this may not be true anymore.
       ;-)

    Andriy Tkachuk wrote:
    > 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"

                                             Jonny

    -- 
    João Carlos Mendes Luís - Networking Engineer - jonny@jonny.eng.br
    _______________________________________________
    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: Eric Kjeldergaard: "Re: sched_4bsd.c Quantum change"

    Relevant Pages

    • Re: Discovering variable types...
      ... >memory it points to is on the heap. ... sequentially reading data, if one is randomly reading records, then a ... >project is what's prompting me to improve disk access. ... from a memory buffer I can do it in about a second. ...
      (comp.lang.pascal.delphi.misc)
    • Re: High Avg. Disk Queue Length - Memory Mapped File
      ... the buffer and give it to your device to fill. ... I shall decide the size of frame and set it to the hardware. ... there are other applications that need the ... One with Serial ATA Hard disk and another with Parallel ...
      (microsoft.public.win32.programmer.kernel)
    • Re: giving up on 1 buffers error messsage
      ... > buffer cache was not successfully flushed to disk, ... > 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 ... > (not during shutdown, but to take a checkpoint), so I am not sure if that ...
      (freebsd-hackers)
    • Re: High-Speed TCP/IP Message Logging
      ... I do like the suggestion about compression and will investigate it. ... Steven's books provides a table of various buffer sizes against timings ... If it's the disk that is the bottleneck and not the CPU you might try ... on three separate sockets each at around a rate of 10Hz of size ...
      (comp.unix.programmer)
    • Re: O_DIRECT question
      ... kick the disk out of the array before the OS ever notices. ... It suffices to say that due to the semantics of writeand sound engineering practice, the application expects to be notified of errors so it can try to recover, or fail gracefully. ... An fsync() flushes all dirty buffers in an undefined order. ... The large buffer size really has little to do with it, rather it is the fact that the writes to null do not block dd from making the next read for any length of time. ...
      (Linux-Kernel)