From owner-freebsd-questions@freebsd.org  Tue Jan 19 17:16:55 2016
Return-Path: <owner-freebsd-questions@freebsd.org>
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 85727A8641F
 for <freebsd-questions@mailman.ysv.freebsd.org>;
 Tue, 19 Jan 2016 17:16:55 +0000 (UTC) (envelope-from yuri@rawbw.com)
Received: from shell1.rawbw.com (shell1.rawbw.com [198.144.192.42])
 by mx1.freebsd.org (Postfix) with ESMTP id 70A7E1619
 for <freebsd-questions@freebsd.org>; Tue, 19 Jan 2016 17:16:55 +0000 (UTC)
 (envelope-from yuri@rawbw.com)
Received: from yuri.doctorlan.com (c-50-184-63-128.hsd1.ca.comcast.net
 [50.184.63.128]) (authenticated bits=0)
 by shell1.rawbw.com (8.15.1/8.15.1) with ESMTPSA id u0JHGjxw010966
 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO);
 Tue, 19 Jan 2016 09:16:45 -0800 (PST) (envelope-from yuri@rawbw.com)
X-Authentication-Warning: shell1.rawbw.com: Host
 c-50-184-63-128.hsd1.ca.comcast.net [50.184.63.128] claimed to be
 yuri.doctorlan.com
Subject: Re: "fsck -y /" keeps saying "Disk is still dirty" no matter how many
 times I run it
To: Matt Smith <matt.xtaz@gmail.com>, Quartz <quartz@sneakertech.com>,
 Polytropon <freebsd@edvax.de>,
 FreeBSD Questions <freebsd-questions@freebsd.org>
References: <569017FF.9060509@rawbw.com>
 <alpine.BSF.2.20.1601081810070.15411@abbf.ynefrvtuareubzr.pbz>
 <20160109012909.6e9b257e.freebsd@edvax.de> <569D6E74.2030606@sneakertech.com>
 <569DB264.6040007@rawbw.com> <20160119092514.GA58286@xtaz.uk>
From: Yuri <yuri@rawbw.com>
Message-ID: <569E6F7E.6000705@rawbw.com>
Date: Tue, 19 Jan 2016 09:16:46 -0800
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101
 Thunderbird/38.4.0
MIME-Version: 1.0
In-Reply-To: <20160119092514.GA58286@xtaz.uk>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Jan 2016 17:16:55 -0000

On 01/19/2016 01:25, Matt Smith wrote:
>
> Yep. When I had SU+J enabled I could never get fsck to ever mark the 
> disk as clean. It was permanently dirty with errors that it claimed it 
> fixed but then you ran it again and the same errors came back. Only 
> way to fix it was to switch off journalling and just leave softupdates 
> only enabled. Then fsck marked the disk as clean as you would expect. 
> I still to this day don't understand why SU+J is the default when it's 
> clearly so broken. 

For me fsck eventually labeled the disk 'clean' after a few dozen runs. 
Would be much more convenient if fsck had an option "to run until clean".

Yuri