Date: Fri, 18 Dec 2009 16:42:31 +0300 From: =?KOI8-R?B?78zFxyDwxdTSwd6j1w==?= <cronfy@gmail.com> To: Konrad Heuer <kheuer2@gwdg.de>, freebsd-questions <freebsd-questions@freebsd.org> Subject: Re: FreeBSD is too filesystem errors sensitive Message-ID: <d4ac64920912180542r59325a60x15124096285dbed@mail.gmail.com> In-Reply-To: <20091208132720.G67127@gwdu60.gwdg.de> References: <4B1DF953.4050504@sprinthost.ru> <hfl7v5$f9j$1@ger.gmane.org> <4B1E2D40.9060900@sprinthost.ru> <20091208114509.B67127@gwdu60.gwdg.de> <4B1E33CF.1070309@sprinthost.ru> <20091208113023.GA1828@owl.midgard.homeip.net> <20091208132720.G67127@gwdu60.gwdg.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Konrad, Erik, thank you for the good advice. Several foreground fsck
in a row really helped.
Konrad, which hardware are you using with FreeBSD on heavily loaded
and i/o-bound systems?
>> If you have other instances of filesystem corruption (which includes
>> everything which can trigger a kernel panic) you need to use a foreground
>> fsck to fix it.
>
> That's true. You should go down to single user mode by entering "shutdown
> now", unmount your filesystems ("umount -a -t ufs") and check your
> filesystem by "fsck -y". Please read "man fsck" before since implicitly
> answering all questions with yes by "-y" may cause loss of data !!!
>
> (To tell the truth: You probably have to do so anyway.)
>
>> Personally I would recommend not using background fsck at all unless you
>> know exactly what you are doing and why.
--
// cronfy
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d4ac64920912180542r59325a60x15124096285dbed>