From owner-freebsd-questions@FreeBSD.ORG Mon Oct 14 18:33:15 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 0DE8A5F8 for ; Mon, 14 Oct 2013 18:33:15 +0000 (UTC) (envelope-from tomek.cedro@gmail.com) Received: from mail-qa0-x231.google.com (mail-qa0-x231.google.com [IPv6:2607:f8b0:400d:c00::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id BFE452D3B for ; Mon, 14 Oct 2013 18:33:14 +0000 (UTC) Received: by mail-qa0-f49.google.com with SMTP id i13so2659060qae.1 for ; Mon, 14 Oct 2013 11:33:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=QQY07PU6KX4m58vFFymNeg0EUaBN5/z9Oqt3SUXgi+E=; b=WZ9xaqkuiCAk9rI3P1iTst+ZmTLxFTbttGRLVlYmFZ3YYCLEziRV66Ac/ciVsDchvD GaRsYe+8CNu0r0H+sgD+ilThNCtjn4qsP9jQgkeg4IaTpeN3uXcXcp2UWKGtlJuMxV2W S5xo6A9lIfsInzPbutCGbPeyZmzsh8F9lRKCIIf9S5LPIOI7rUPInoGIt8HKk8nMf5KC nC942iMQm1Nd3eN3mMQPDRNmf7M/tPTluc3wH4RSAFSyokWaZhas7AqRSC9BN1MtD2m6 zBq2akQSetVa4dncAT6xYb85c6OANX2KrTgoYppR/1BSnyyBjrSwSFuTeufV7HtY1Xvu Jt0Q== MIME-Version: 1.0 X-Received: by 10.224.160.83 with SMTP id m19mr3927553qax.108.1381775593943; Mon, 14 Oct 2013 11:33:13 -0700 (PDT) Sender: tomek.cedro@gmail.com Received: by 10.49.16.170 with HTTP; Mon, 14 Oct 2013 11:33:13 -0700 (PDT) In-Reply-To: <525C2FBC.4080808@cran.org.uk> References: <525A6831.5070402@gmail.com> <20131014133953.58f74659@gumby.homeunix.com> <525C1D1C.9050708@gmail.com> <525C2554.7080203@pchotshots.com> <525C2FBC.4080808@cran.org.uk> Date: Mon, 14 Oct 2013 20:33:13 +0200 X-Google-Sender-Auth: cDmHk80YkSEIGokyXuXjwCqEWi8 Message-ID: Subject: Re: SU+J Lost files after a power failure From: CeDeROM To: Bruce Cran Content-Type: text/plain; charset=UTF-8 Cc: David Demelier , Adam Vande More , Brad Mettee , FreeBSD Questions X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Oct 2013 18:33:15 -0000 On Mon, Oct 14, 2013 at 7:54 PM, Bruce Cran 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