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>
next in thread | previous in thread | raw e-mail | index | archive | help
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, ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160119182657.0d59e76b.freebsd>