From owner-freebsd-questions@freebsd.org  Sat Jan 23 19:16:23 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 13729A8E735
 for <freebsd-questions@mailman.ysv.freebsd.org>;
 Sat, 23 Jan 2016 19:16:23 +0000 (UTC)
 (envelope-from patrickhess@gmx.net)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.19])
 (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-1" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 66C1C18C8
 for <freebsd-questions@freebsd.org>; Sat, 23 Jan 2016 19:16:21 +0000 (UTC)
 (envelope-from patrickhess@gmx.net)
Received: from desk8.phess.net ([95.88.166.205]) by mail.gmx.com (mrgmx001)
 with ESMTPSA (Nemesis) id 0MGS9o-1aIfwD2Ze4-00DDtA for
 <freebsd-questions@freebsd.org>; Sat, 23 Jan 2016 20:16:13 +0100
From: Patrick Hess <patrickhess@gmx.net>
To: freebsd-questions@freebsd.org
Subject: Re: "fsck -y /" keeps saying "Disk is still dirty" no matter how many
 times I run it
Date: Sat, 23 Jan 2016 20:16:11 +0100
Message-ID: <1553395.JCnJngLWQk@desk8.phess.net>
User-Agent: KMail/4.14.3 (FreeBSD/10.1-RELEASE-p26; KDE/4.14.3; i386; ; )
In-Reply-To: <CAA2O=b_gsMDb+tZt657YN+_Yf6NN-kiOUdhNifE+=PzS9Ej+cQ@mail.gmail.com>
References: <569017FF.9060509@rawbw.com> <569E6F7E.6000705@rawbw.com>
 <CAA2O=b_gsMDb+tZt657YN+_Yf6NN-kiOUdhNifE+=PzS9Ej+cQ@mail.gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-Provags-ID: V03:K0:GaqmIgeWHHCUcHcDCZJgg0yUWv8DMCLbiysmR+TQ3jGhv8E/4w/
 kmjUNJMMkzrjysaLqbpoZinoPJaKB/mVhq4MTRTyrozTPge0Lv1ZV998S7UbLlN/YqsdUOn
 TJlcBu8UuBVfD4HwKVUh9rjEfVjghlN8q0YBr3WPsszPUNmKdAFpPCqoSmAZ84FoqSEKpJd
 UEkrwB06SQuILoGyexCJg==
X-UI-Out-Filterresults: notjunk:1;V01:K0:B0hLbCl+cIs=:hTugGNPd5g5Ywr67B+z1mM
 pJnn4D1T5pXEd5uziyjlZfvPYreFEcKSvZwX4AEv/FjSvAWNUozL3XuN7Y+4hTAuG0PSXnIJp
 MAzG0uvgEEgzd/JCMAmlX3btxTx5m6yqAzexsUNSDEtSExkFj6MMNh55C7HK0BphWKm/dp63e
 7sTrfx1VRJh9TfATuAU6kCLBvm/DvCLJ4ElKUvOG5uAnrh5VNahY/urivVzFsmiyFZH1/IIrq
 PrT2emMz8HgG+mTRiIpOGiwy/tBzincDva/+rdJy0mzC7ci/zFUvPb+l7nfc6RuwpeWdEsJ9I
 jI9xpqQdU/VHf4UGI8SFZUhaaG2uMhyoxHZK+FFUe4WEcu+nxLg10+S9gBboOJ+Ecpnk7JRPD
 dOuyltKrFBESe3TxyGRGEqZuo1tXQpBWcnVQR8efHn9wKXZmQAfDCvfR7p29WzEtY+cJSamcD
 +F3nl8npPkYCdxHjA9Doi/I3lS01mut1Ii+RsQV5Fm675CzXUh4cmn9aDuMfXi8zfOyGn6ld3
 9FXezkClESGoWFm6GnESppP2Jra1kJQb0VAcrxHYKRRTcRnM+jTcyxbEdVMVRuu1bTnX9EUqW
 jLC+4BdXBCXo9VYJzMuH6zbNEGdP309/e1SFLXfvieVSCxMVNgoneGXzB0hPmDDc1lBESQlyG
 OPygs6zPjritjW9BT+ghockHpE7CJAPcykHkVRY7zOl6wj3fVNgP2lyRyIh3Jf+EM0OBetX7l
 KE1/t56miTiZV+1wzCDbO4ywVvKFpU/1Q2EPlf+7xSqGNoNdg+d+Dz3rQcmNEHTnWaFrEcurl
 NGmeuKY
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: Sat, 23 Jan 2016 19:16:23 -0000

Anton Sayetsky wrote:
> Would be much more convenient if fsck had an option "to run until clean".
> Maybe something like this will work (completely untested):
> while(result);do fsck ...; result=$?; done

This should do the trick:

    until fsck ...; do :; done

Matt Smith wrote:
> When I had SU+J enabled I could never get fsck to ever mark the 
> disk as clean.

I've been using SU+J since the early days of 9.x and never encountered
any such issues.

Patrick