From owner-freebsd-hackers@FreeBSD.ORG Fri Feb 18 23:24:06 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 BD31616A4CE for ; Fri, 18 Feb 2005 23:24:06 +0000 (GMT) Received: from mail-svr1.cs.utah.edu (brahma.cs.utah.edu [155.98.64.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3942C43D5A for ; Fri, 18 Feb 2005 23:24:06 +0000 (GMT) (envelope-from saggarwa@cs.utah.edu) Received: from localhost (localhost [127.0.0.1]) by mail-svr1.cs.utah.edu (Postfix) with ESMTP id D4C273482D for ; Fri, 18 Feb 2005 16:24:05 -0700 (MST) Received: from mail-svr1.cs.utah.edu ([127.0.0.1]) by localhost (mail-svr1.cs.utah.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 21982-03 for ; Fri, 18 Feb 2005 16:24:05 -0700 (MST) Received: from antitrust.cs.utah.edu (antitrust.cs.utah.edu [155.98.65.29]) by mail-svr1.cs.utah.edu (Postfix) with ESMTP id 90B3B34778 for ; Fri, 18 Feb 2005 16:24:05 -0700 (MST) Received: by antitrust.cs.utah.edu (Postfix, from userid 4973) id 76DC5108E2F; Fri, 18 Feb 2005 16:24:05 -0700 (MST) Received: from localhost (localhost [127.0.0.1]) by antitrust.cs.utah.edu (Postfix) with ESMTP id 6BA00108E2E for ; Fri, 18 Feb 2005 16:24:05 -0700 (MST) Date: Fri, 18 Feb 2005 16:24:05 -0700 (MST) From: Siddharth Aggarwal To: freebsd-hackers@freebsd.org In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: amavisd-new at cs.utah.edu X-Mailman-Approved-At: Sat, 19 Feb 2005 13:26:58 +0000 Subject: 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, 18 Feb 2005 23:24:06 -0000 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?