Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 14 Oct 2013 22:40:29 +0200
From:      David Demelier <demelier.david@gmail.com>
To:        freebsd-questions@freebsd.org
Subject:   Re: SU+J Lost files after a power failure
Message-ID:  <525C56BD.8060706@gmail.com>
In-Reply-To: <20131014190850.355ecd63@gumby.homeunix.com>
References:  <525A6831.5070402@gmail.com> <l3gc7e$c91$1@ger.gmane.org> <20131014133953.58f74659@gumby.homeunix.com> <525C1D1C.9050708@gmail.com> <20131014190850.355ecd63@gumby.homeunix.com>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On 14.10.2013 20:08, RW wrote:
> On Mon, 14 Oct 2013 18:34:36 +0200
> David Demelier wrote:
> 
>> On 14.10.2013 14:39, RW wrote:
> 
>>> If you are having problems with data integrity you might try
>>> gjournal or zfs instead.
>>
>> Why? SU+J is enabled by default. Isn't the purpose of a journaled file
>> system to ensure that any bad shutdown will protect data?
> 
> SU+J isn't a journalled filesytem, it's a filesystem with soft-updates
> that journals information about free space so it can be recovered
> without having to go through the whole filesystem.
> 

Okay, but why the fsck didn't run by itself to detect that the journal
didn't replayed correctly (if I understanding well) to correct the issues?




Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?525C56BD.8060706>