Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 14 Oct 2013 13:43:40 -0500
From:      Adam Vande More <amvandemore@gmail.com>
To:        CeDeROM <cederom@tlen.pl>
Cc:        Bruce Cran <bruce@cran.org.uk>, David Demelier <demelier.david@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:  <CA%2BtpaK1_sV6upk37RdkkxWs7YDRTQ-Fw-H%2BzxbN4KBtmzCYATA@mail.gmail.com>
In-Reply-To: <CAFYkXj==tiKSAJh3kkCnonsqAaDg_sHYYEUnfLKWLaR-GD-Nzw@mail.gmail.com>
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> <CAFYkXj==tiKSAJh3kkCnonsqAaDg_sHYYEUnfLKWLaR-GD-Nzw@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Oct 14, 2013 at 1:33 PM, CeDeROM <cederom@tlen.pl> wrote:

> Thank you for explaining :-) So it looks that it would be sensible to
> force filesystem check every n-th mount..?


Please explain the logic in which this helps anything.


> Or to do a filesystem check
> after crash..?


Already standard behavior as implicitly seen in this thread.


> Are there any flags like that to mark filesystem
> unclean and to force fsck after n-th mount?


No and any fs that requires such a system is broken by design.


> 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?
>

mount -o sync or use ZFS. Both require hardware that correctly report
success to fsync.

-- 
Adam Vande More



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2BtpaK1_sV6upk37RdkkxWs7YDRTQ-Fw-H%2BzxbN4KBtmzCYATA>