From owner-freebsd-questions@freebsd.org Sat Jul 25 11:32:53 2015 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4A76D9AAB8E for ; Sat, 25 Jul 2015 11:32:53 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "wonkity.com", Issuer "wonkity.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id EE9381E7D for ; Sat, 25 Jul 2015 11:32:52 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.15.2/8.15.2) with ESMTPS id t6PBWjfJ036349 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 25 Jul 2015 05:32:45 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.15.2/8.15.2/Submit) with ESMTP id t6PBWjoS036346; Sat, 25 Jul 2015 05:32:45 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Sat, 25 Jul 2015 05:32:45 -0600 (MDT) From: Warren Block To: CK cc: freebsd-questions@freebsd.org Subject: Re: Endless Data Loss In-Reply-To: <0MRCCJ-1ZUCcr1rAt-00UeQk@mail.gmx.com> Message-ID: References: <0MRCCJ-1ZUCcr1rAt-00UeQk@mail.gmx.com> User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Sat, 25 Jul 2015 05:32:45 -0600 (MDT) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Jul 2015 11:32:53 -0000 On Fri, 24 Jul 2015, CK wrote: > PS. One thing I notice is that if I ever ensure correct permissions > of the .sujournal files, but setting them to the same values that > they already have, upon reboot I get an error message to the effect > "timestamp on journal doesn't match last mount time", and then there > is a fallback to a full fsck, most always followed by some cleared > inodes and file loss. Helpful hint or not, I don't know. Step 1: stop using SUJ, soft updates journaling. Switch to just soft updates. This can be done from single user mode with 'tunefs -j disable'. As far as the rest, the description of what happens and when is not clear. Is the machine subject to sudden power loss?