Date: Sun, 8 Aug 1999 14:49:21 -0700 From: "Morgan Davis" <mdavis@cts.com> To: "Tom" <tom@uniserve.com>, "David Malone" <dwmalone@maths.tcd.ie> Cc: <freebsd-stable@freebsd.org> Subject: RE: Removing files in /lost+found causes panic Message-ID: <NABBLJGKKPMOKACIENPPIEOGCHAA.mdavis@cts.com> In-Reply-To: <Pine.BSF.4.02A.9908080919250.26669-100000@shell.uniserve.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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 Tom, fsck has been run several times (multiples in single user mode, with syncs in between, and across several reboots), and shows no problems at all. Yet, any attempt to molest the files in /lost+found initiates an immediate panic. I think the clri method might be the best way, and I'll try that next. SCO has an unlink command that sounds like it does the same thing, only you pass it a file or directory name. Just takes it out and the next fsck cleans up after you. --Morgan 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?NABBLJGKKPMOKACIENPPIEOGCHAA.mdavis>