Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 08 Dec 2009 14:09:03 +0300
From:      cronfy <cronfy@sprinthost.ru>
To:        freebsd-questions@freebsd.org
Subject:   Re: FreeBSD is too filesystem errors sensitive
Message-ID:  <4B1E33CF.1070309@sprinthost.ru>
In-Reply-To: <20091208114509.B67127@gwdu60.gwdg.de>
References:  <4B1DF953.4050504@sprinthost.ru> <hfl7v5$f9j$1@ger.gmane.org> <4B1E2D40.9060900@sprinthost.ru> <20091208114509.B67127@gwdu60.gwdg.de>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help

>>>>  panics like 'freeing free block' or 'ffs_valloc: dup alloc'
>>
>> Is there a way to say "Dear kernel, don't panic, I'am holding your 
>> hand, keep working please-please-please?" If so, can it lead to 
>> complete filesystem corruption indeed or it is not so serious?
>
> Afaik you can't do this. And you shouldn't do if it'd be possible. The 
> file system errors you mention above should not happen under any 
> normal circumstances. They may happen after a crash caused by other 
> reasons but should get repaired by fsck. The kernel cannot continue 
> with such errors because the whole file system metadata cannot be 
> trusted anymore until repaired.
>
Thanks.

What I can definitely state is that after reboot nothing will get any 
better. I will have same filesystem with same errors + new errors that 
appeared because soft-updates were not synced, and I will have fsck 
running in background. I'd prefer to just start fsck in background, 
skipping that annoying reboot phase ;-) Am I willing strange?





Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?4B1E33CF.1070309>