Date: Thu, 04 Mar 1999 17:58:48 +0100 From: Roelof Osinga <roelof@eboa.com> To: Chris Tubutis <chris@tci.com> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Have crashed, won't travel Message-ID: <36DEBBC8.6B5B5EDD@eboa.com> References: <36DCB59E.F16D5539@eboa.com> <19990303195632.B441@lemis.com> <36DDBFEB.86D89D20@eboa.com> <19990304095813.I441@lemis.com> <36DDEFFD.A4DB4978@eboa.com> <19990304130126.B441@lemis.com> <36DE0352.E99BCB70@eboa.com> <36DEA481.7ABA8AF3@tci.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Chris Tubutis wrote: > > Recently, I accidentally knocked the power swich on my 'puter just enough > for the machine to decide to reboot itself. On the way back up, it made > me run fsck manually; fsck proceeded to "fix" things (the primary complaints > I seem to remember were two entries for single files and files not being > allocated the correct amount of space) and put close to 200 files in > /lost+found. It's fairly difficult and/or time consuming to figure out > the old names of files in /lost+found (I think they were now given names > representing inode numbers) and where they used to live, so much so that > the best course of action for me was to either restore from a full backup > or reinstall from the original media. While corruption in unix filesystems > may be rare, when it happens, it happens with spectacular glory. Precisely. In my case I've been running slackware Linux the last few years. Have had a couple of power outages, but no errors whatsoever were reported. Either because there weren't any due to regular syncing or because of an inefficient fsck. In the few weeks I've tried xBSDs (again :) I had at least two power failures and both times fsck reported errors. That makes me nervous, more so because I don't have real FreeBSD experience so I can't compare it to a True Crash. And when you read the man page (see, I do read them) it says: The kernel takes care that only a restricted class of innocuous filesys- tem inconsistencies can happen unless hardware or software failures in- tervene. These are limited to the following: It is of course the frase "unless hardware ... failures intervene" that describes my situation. In effect it tells you not to worry ... unless you've had, say, a power outage. Still, I don't even have the lost+found dirs so in all likeliness it was indeed a bit of structural damage that was easily repaired. Think I'll bring it down and do one last check (using -f :). Then chalk it up as learning experience. Roelof -- Home is where the (@) http://eboa.com/ is. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?36DEBBC8.6B5B5EDD>