From owner-freebsd-questions@freebsd.org  Tue Jan 19 17:27:01 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 0D7D9A86A14
 for <freebsd-questions@mailman.ysv.freebsd.org>;
 Tue, 19 Jan 2016 17:27:01 +0000 (UTC)
 (envelope-from freebsd@edvax.de)
Received: from mx01.qsc.de (mx01.qsc.de [213.148.129.14])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id C87FF1FF3
 for <freebsd-questions@freebsd.org>; Tue, 19 Jan 2016 17:27:00 +0000 (UTC)
 (envelope-from freebsd@edvax.de)
Received: from r56.edvax.de (port-92-195-101-208.dynamic.qsc.de
 [92.195.101.208])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mx01.qsc.de (Postfix) with ESMTPS id 5852F3CFFF;
 Tue, 19 Jan 2016 18:26:57 +0100 (CET)
Received: from r56.edvax.de (localhost [127.0.0.1])
 by r56.edvax.de (8.14.5/8.14.5) with SMTP id u0JHQvIi002932;
 Tue, 19 Jan 2016 18:26:57 +0100 (CET)
 (envelope-from freebsd@edvax.de)
Date: Tue, 19 Jan 2016 18:26:57 +0100
From: Polytropon <freebsd@edvax.de>
To: Yuri <yuri@rawbw.com>
Cc: Matt Smith <matt.xtaz@gmail.com>, Quartz <quartz@sneakertech.com>,
 FreeBSD Questions <freebsd-questions@freebsd.org>
Subject: Re: "fsck -y /" keeps saying "Disk is still dirty" no matter how
 many times I run it
Message-Id: <20160119182657.0d59e76b.freebsd@edvax.de>
In-Reply-To: <569E6F7E.6000705@rawbw.com>
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> <569E6F7E.6000705@rawbw.com>
Reply-To: Polytropon <freebsd@edvax.de>
Organization: EDVAX
X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
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:27:01 -0000

On Tue, 19 Jan 2016 09:16:46 -0800, Yuri wrote:
> 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".

For most cases, one run of "fsch -yf" will accomplish this.
A second run usually fixes the edge cases...


-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...