From owner-freebsd-stable Sun Aug 8 14:51:56 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (Postfix) with SMTP id CD99214F9C for ; Sun, 8 Aug 1999 14:51:53 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 11Dapc-00025J-00; Sun, 8 Aug 1999 14:50:16 -0700 Date: Sun, 8 Aug 1999 14:50:13 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: David Malone Cc: Morgan Davis , freebsd-stable@freebsd.org Subject: Re: Removing files in /lost+found causes panic In-Reply-To: <19990808224135.A54409@walton.maths.tcd.ie> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 8 Aug 1999, David Malone wrote: > On Sun, Aug 08, 1999 at 09:21:15AM -0700, Tom wrote: > > > I don't think you should ever need to use clri. The system should only > > panic if the filesystem is corrupt. If fsck finds serious damage, you > > should run it again to make sure everything. Chances are the first fsck > > left some unfixed problems. > > I've definitely come up with times where: > > 1) fsck checks the filesystem and gives it the OK, but it isn't. Yes, but is this a -p", which only does a partial check? If so, that may be what it is supposed to do. > 2) fsck leaves weird files around in /lost+found which are difficult > or impossible to delete. > 3) fsck after about 8 runs still goes through the same list of questions > and asks to be rerun again. > 4) fsck says it doesn't need to be rerun, but if you rerun it it makes > more repairs. A lot of these sound like hardware. Some drives, especially IDE, will just corrupt themselves. Turing off multi-block mode can somtimes help. I have a Maxtor IDE drive (8.4GB) that I can not use with FreeBSD's multi-block mode, as data will be corrupted and fsck will always report errors. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message