Date: Sun, 8 Aug 1999 16:30:14 -0700 From: "Morgan Davis" <mdavis@cts.com> To: "Mike Smith" <mike@smith.net.au> Cc: <freebsd-stable@freebsd.org> Subject: RE: Removing files in /lost+found causes panic Message-ID: <NABBLJGKKPMOKACIENPPAEOICHAA.mdavis@cts.com> In-Reply-To: <199908082302.QAA13667@dingo.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> It would, of course, have been _really_nice_ if you actually bothered > to give us some details on these files before you nuked them... Sorry, will keep that in mind if it happens again. Getting a clean system back up and running was the main thing on my mind. What steps do you recommend so I can get you the details you need? Not sure if this will be useful, but here's all I can tell you. I became aware of a problem during a tape backup. Dump complained about invalid file references. I stopped the backup when it indicated that the completion time was going to be over 800 hours (normally, it's about an hour). After getting into single user, I ran fsck which found a lot of errors. This put about a dozen files into lost+found directories on two filesystems. The files were mostly small -- between 60 and a couple hundred bytes. They appeared to be from files in /usr/src/contrib and a few in /usr/obj. (Nothing I couldn't restore from a cvsup and a make world). The modes, owner, group, and flags were scrambled nonsense -- there are no files on any healthy system with those attributes. I cleared out all the flags with chflags. I could clear all the modes except the special device type bits (block and character). Any attempt to remove the files resulted in a panic. However, subsequent fsck's would run through everything with no errors (except for the dirty filesystem warning, of course). I booted the FreeBSD install floppies and use the Fixit disk to try to remove the files from there, thinking maybe the fact that they were on the same filesystem as the kernel was the culprit. But after mounting the drives, attempts to remove the files resulted in similar panics. Finally, David Malone's suggestion to use clri + fsck was the magic to clean it all up. --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?NABBLJGKKPMOKACIENPPAEOICHAA.mdavis>