Date: Thu, 6 Aug 2009 11:54:56 +0200 From: Christian Walther <cptsalek@gmail.com> To: Matthias Andree <ma@dt.e-technik.tu-dortmund.de> Cc: Cristiano Deana <cristiano.deana@gmail.com>, freebsd-stable@freebsd.org Subject: Re: Turn off rebooting in single-user mode after fail. Message-ID: <14989d6e0908060254k7c3deceap27d6c4d0c582cef9@mail.gmail.com> In-Reply-To: <op.ux8g5r1xt6kky0@merlin.emma.line.org> References: <659cf8870907270259m2e23769dxf416a3c86f9e8c50@mail.gmail.com> <d8a4930a0907270355o2ef07c88hb93c05c48d1af0b6@mail.gmail.com> <op.ux8g5r1xt6kky0@merlin.emma.line.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi 2009/8/6 Matthias Andree <ma@dt.e-technik.tu-dortmund.de>: > Probably not fsck's fault, but if there is a major file system corruption, > it can wreak havoc. Yes, it can. But on the other hand the question is if one is capable of dealing with a major file system corruption during a manual fsck run. It requires in depth knowledge of the filesystem specification, and what each question really means. The whorst case I've seen so far was a linux ext2 FS that wiped entirely by fsck. Nearly 200GB of data were lost and had to be restored from the last backup. I personally like fsck -y (because I certainly don't have this knowledge) and pray that my FS comes out intact. If it doesn't, well, it's time to do a restore. ;-) Christian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14989d6e0908060254k7c3deceap27d6c4d0c582cef9>