Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 14 Oct 2013 20:33:13 +0200
From:      CeDeROM <cederom@tlen.pl>
To:        Bruce Cran <bruce@cran.org.uk>
Cc:        David Demelier <demelier.david@gmail.com>, Adam Vande More <amvandemore@gmail.com>, Brad Mettee <bmettee@pchotshots.com>, FreeBSD Questions <freebsd-questions@freebsd.org>
Subject:   Re: SU+J Lost files after a power failure
Message-ID:  <CAFYkXj==tiKSAJh3kkCnonsqAaDg_sHYYEUnfLKWLaR-GD-Nzw@mail.gmail.com>
In-Reply-To: <525C2FBC.4080808@cran.org.uk>
References:  <525A6831.5070402@gmail.com> <l3gc7e$c91$1@ger.gmane.org> <20131014133953.58f74659@gumby.homeunix.com> <525C1D1C.9050708@gmail.com> <CA%2BtpaK2Pr2po2cQ1yanQK9%2BwLp77SYqYHjxiXaU5FfXwHrkGow@mail.gmail.com> <CAFYkXjn-1wTJcQ4a_fyXCvwh9ukt3%2BdjM2qsMeaH1HhVJNvhiA@mail.gmail.com> <525C2554.7080203@pchotshots.com> <CAFYkXjm8y0Br31_pqRZc0sNFbqCNtKHhjeQuiLXkGT2zxSu0GA@mail.gmail.com> <525C2FBC.4080808@cran.org.uk>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Oct 14, 2013 at 7:54 PM, Bruce Cran <bruce@cran.org.uk> wrote:
> On 10/14/2013 6:16 PM, CeDeROM wrote:
>> Isn't there Journal to prevent and reverse such damage?
>
> Unlike other journaling filesystems, UFS+J only protects the metadata, not
> the data itself - i.e. I think it ensures you won't have to run a manual
> fsck, but just like plain old UFS files may be truncated as the journal is
> replayed.

Thank you for explaining :-) So it looks that it would be sensible to
force filesystem check every n-th mount..? Or to do a filesystem check
after crash..? Are there any flags like that to mark filesystem
unclean and to force fsck after n-th mount? That would assume
disabling journal and soft updates journaling I guess..?

What would be the best option for best data integrity in case of
crash? That would be helpful for development systems I guess :-)

-- 
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFYkXj==tiKSAJh3kkCnonsqAaDg_sHYYEUnfLKWLaR-GD-Nzw>