"fsck -y /" keeps saying "Disk is still dirty" no matter how many times I run it

Polytropon freebsd at edvax.de
Tue Jan 19 17:27:01 UTC 2016

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...

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

More information about the freebsd-questions mailing list