From owner-freebsd-stable@FreeBSD.ORG Thu Dec 4 20:42:28 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1243416A4CE for ; Thu, 4 Dec 2003 20:42:28 -0800 (PST) Received: from lariat.org (lariat.org [63.229.157.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id AF78F43FB1 for ; Thu, 4 Dec 2003 20:42:26 -0800 (PST) (envelope-from brett@lariat.org) Received: from runaround.lariat.org (IDENT:ppp1000.lariat.org@lariat.org [63.229.157.2]) by lariat.org (8.9.3/8.9.3) with ESMTP id VAA29343; Thu, 4 Dec 2003 21:42:18 -0700 (MST) X-message-flag: Warning! Use of Microsoft Outlook renders your system susceptible to Internet worms. Message-Id: <6.0.0.22.2.20031204212410.04c85d10@localhost> X-Sender: brett@localhost (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22 Date: Thu, 04 Dec 2003 21:40:38 -0700 To: Igor Pokrovsky From: Brett Glass In-Reply-To: <20031205041354.GA1093@doom.homeunix.org> References: <200312040413.VAA14830@lariat.org> <20031205041354.GA1093@doom.homeunix.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" cc: stable@freebsd.org Subject: Re: Panic during kernel rebuild; file system left inconsistent X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Dec 2003 04:42:28 -0000 At 09:13 PM 12/4/2003, Igor Pokrovsky wrote: >I've seen the same message about softupdates, but it appeared after unexpected >power problems, when computer turned off without syncs and umounts. In this case, it occurred after a crash... which likewise occurred without a sync or umount. The machine just panicked and rebooted. When I got to the console, I found it in single-user mode, with fsck complaining that softupdates hadn't kept things consistent and asking me what to do with shards of files whose metadata hadn't been fully committed to disk. After two fscks, the file system appeared to be fine; all of the files in "lost+found" were dependency files generated during the kernel build and could be deleted safely. But the crash unnerved me. If the system is so fragile that it crashes during a kernel rebuild, how will it react to other stresses? Since there have been rumblings about problems in the 4-STABLE ata driver, I wonder if perhaps I should go with pst, twe, or SCSI controllers to increase stability in systems I build until 5.3 comes out. --Brett