From owner-freebsd-hackers@FreeBSD.ORG Fri Feb 25 08:17:03 2005 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A52C116A4CE for ; Fri, 25 Feb 2005 08:17:03 +0000 (GMT) Received: from mail.emict.com (brig.emict.com [212.90.172.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3C6CE43D2F for ; Fri, 25 Feb 2005 08:17:00 +0000 (GMT) (envelope-from andrit@ukr.net) Received: from BORJA (unknown [203.199.120.221]) by mail.emict.com (Postfix) with ESMTP id EC8652E35D for ; Fri, 25 Feb 2005 10:16:45 +0200 (EET) Message-ID: <00c601c51b12$5a9f0760$090210ac@BORJA> From: "Andriy Tkachuk" To: References: Date: Fri, 25 Feb 2005 13:46:30 +0530 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Subject: Re: giving up on 1 buffers error messsage X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Feb 2005 08:17:03 -0000 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" > >