From owner-freebsd-questions@FreeBSD.ORG Mon Oct 14 18:43:40 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 BDFCD83F for ; Mon, 14 Oct 2013 18:43:40 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: from mail-pa0-x232.google.com (mail-pa0-x232.google.com [IPv6:2607:f8b0:400e:c03::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 939AF2E00 for ; Mon, 14 Oct 2013 18:43:40 +0000 (UTC) Received: by mail-pa0-f50.google.com with SMTP id fb1so7806241pad.23 for ; Mon, 14 Oct 2013 11:43:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Wi/0MjFSUzV7WB3LMvRnfI79QOw/XXn3rxhdvjJwgVw=; b=XlLLskuKyxhD/rm6WRQHQuCT0BJ48b3OSPzbL5/3VjXETE7p431+bu1PH9iKEgA5kD sPsD8dBLzZPd45KDOrZMbyQMi1trQ2v+kyTpRGLi4h8pf7xAOYPYLBlxCxrJeZFhEpfB klvB+xUHZ7b87a73aClF291YXl+8cP+cln7qeLKEp41Ai2SAVFGlxqPEWgkU9Gud9lii Exebpc5SB0Ielx91IB20Rg6iuDI9NTVrT3RtFOPvV/VRf1vZ/CpAWk0bhQa+826vVg7R Giz1xVOpQ7DQKh+gzOoic8CFkhw68wRqwG11lvg78KCt09BOyzffhqp7mscfYdm71jnU xpUg== MIME-Version: 1.0 X-Received: by 10.66.178.143 with SMTP id cy15mr39526628pac.105.1381776220276; Mon, 14 Oct 2013 11:43:40 -0700 (PDT) Received: by 10.70.92.79 with HTTP; Mon, 14 Oct 2013 11:43:40 -0700 (PDT) In-Reply-To: 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 13:43:40 -0500 Message-ID: Subject: Re: SU+J Lost files after a power failure From: Adam Vande More To: CeDeROM Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: Bruce Cran , David Demelier , 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:43:40 -0000 On Mon, Oct 14, 2013 at 1:33 PM, CeDeROM 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