Date: Thu, 04 Mar 1999 08:19:29 -0700 From: Chris Tubutis <chris@tci.com> To: Roelof Osinga <roelof@eboa.com> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Have crashed, won't travel Message-ID: <36DEA481.7ABA8AF3@tci.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>
next in thread | previous in thread | raw e-mail | index | archive | help
Roelof Osinga wrote: > > Well, I can't recollect having ever experienced file corruption with an > unix system but I do have experienced them with other OSs. Also I have > lost whole filesystems due to superblock problems. Granted, this was > with Microsoft Xenix, but ... 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. ct 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?36DEA481.7ABA8AF3>