Date: Sun, 8 Aug 1999 09:21:15 -0700 (PDT) From: Tom <tom@uniserve.com> To: David Malone <dwmalone@maths.tcd.ie> Cc: Morgan Davis <mdavis@cts.com>, freebsd-stable@freebsd.org Subject: Re: Removing files in /lost+found causes panic Message-ID: <Pine.BSF.4.02A.9908080919250.26669-100000@shell.uniserve.ca> In-Reply-To: <19990808141339.A51902@walton.maths.tcd.ie>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 8 Aug 1999, David Malone wrote: > On Sun, Aug 08, 1999 at 04:20:37AM -0700, Morgan Davis wrote: > > > This happens on the root filesystem's lost+found as well as on the /usr > > filesystem (which is the only one that has softupdates enabled). > > With really weird files in lost+found you probably need to use clri > to clear the inodes for these weird files. You could probably try > something like the following: > > 1) ls -i and note the inode numbers. > 2) boot into single user mode. > 3) Do "clri /dev/rda0swhatever 4873928 4287942 37204 ..." > where you put in the correct character device and inode > numbers > 4) Reboot and let fsck clean up the resulting mess. > > We had this happen ages ago when half of a ccd device keep going > away 'cos of confused scsi stuff. > > David. 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. Tom 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?Pine.BSF.4.02A.9908080919250.26669-100000>