Next time you run fsck -y in this scenario, log the output to an md partition and stick it somewhere for analysis. At least, that was the moral of the story last time I hosed a box in this form (incidentally, I think it ended up being a failing hard disk).
Robert N M Watson FreeBSD Core Team, TrustedBSD Projects [EMAIL PROTECTED] Network Associates Laboratories On Fri, 24 Jan 2003, Greg Lehey wrote: > I'm rather astounded. I'm currently at a Linux conference, and have > of course been boasting about the stability of ufs, and today I had a > crash which tore apart my /home file system. > > This is on a laptop, one which has been running -CURRENT for years > with no trouble. At the moment it's running 5.0-RELEASE. Today I > shut it down cleanly, and a couple of hours later rebooted it. It has > three file systems, one of which came up dirty. fsck -y reported > thousands of errors, and when it was finished, my home directory and > some other files were gone, and all the subdirectories of my home > directory were in lost+found, a total of 1.4 GB. Most of the errors > appear to be duplicate Inode numbers. > > Obviously it's too late to work out what happened, but I thought it's > worth mentioning in case somebody else is having the same trouble. > > Greg > -- > See complete headers for address and phone numbers > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
