Date: Tue, 19 Jan 2016 09:25:14 +0000 From: Matt Smith <matt.xtaz@gmail.com> To: Yuri <yuri@rawbw.com> Cc: 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: <20160119092514.GA58286@xtaz.uk> In-Reply-To: <569DB264.6040007@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>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jan 18 19:49, Yuri wrote: >On 01/18/2016 15:00, Quartz wrote: >>Yuri- do you have soft updates AND journaling enabled? I seem to >>recall people repeatedly having problems with fsck stuff not working >>right on SU+J disks. > >Yes. > 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. -- Matt
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160119092514.GA58286>