Date: Mon, 14 Oct 2013 19:40:48 +0100 From: Bruce Cran <bruce@cran.org.uk> To: CeDeROM <cederom@tlen.pl> 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: <525C3AB0.6030609@cran.org.uk> 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 10/14/2013 7:33 PM, CeDeROM wrote: > 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 :-) As I understand it UFS+J gives the same reliability as UFS with a normal fsck after a crash, so on a development system the only ways to improve the situation would be to mount with the 'sync' option, disable write caching on the disk or to switch to a different filesystem like ZFS. -- Bruce Cran
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?525C3AB0.6030609>