Date: Sun, 8 Aug 1999 22:41:35 +0100 From: David Malone <dwmalone@maths.tcd.ie> To: Tom <tom@uniserve.com> Cc: Morgan Davis <mdavis@cts.com>, freebsd-stable@freebsd.org Subject: Re: Removing files in /lost+found causes panic Message-ID: <19990808224135.A54409@walton.maths.tcd.ie> In-Reply-To: <Pine.BSF.4.02A.9908080919250.26669-100000@shell.uniserve.ca>; from Tom on Sun, Aug 08, 1999 at 09:21:15AM -0700 References: <19990808141339.A51902@walton.maths.tcd.ie> <Pine.BSF.4.02A.9908080919250.26669-100000@shell.uniserve.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
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. 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. The first and fourth were a long time ago and I think have been fixed. The second I haven't seen recently, but evidently someone else has. The last has happened to me on 3.2 as recently as a month ago. Clir and fsdb have got me out of these situations. I always run fsck an extra time these days if there was any corruption, just to be safe! David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990808224135.A54409>