Date: Tue, 19 Jan 2016 09:16:46 -0800 From: Yuri <yuri@rawbw.com> To: Matt Smith <matt.xtaz@gmail.com>, Quartz <quartz@sneakertech.com>, Polytropon <freebsd@edvax.de>, 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: <569E6F7E.6000705@rawbw.com> In-Reply-To: <20160119092514.GA58286@xtaz.uk> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?569E6F7E.6000705>