lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Fri, 22 Jan 2010 18:18:11 -0500
From:	tytso@....edu
To:	Ric Wheeler <rwheeler@...hat.com>
Cc:	Andreas Dilger <adilger@....com>,
	Eric Sandeen <sandeen@...hat.com>,
	ext4 development <linux-ext4@...r.kernel.org>,
	Bill Nottingham <notting@...hat.com>
Subject: Re: [PATCH] default max mount count to unused

On Fri, Jan 22, 2010 at 01:57:16PM -0500, Ric Wheeler wrote:
> 
> I think that we have to move towards an assumption that our
> journalling code actually works - the goal should be that we can
> *always* mount after a crash or clean reboot. That should be the
> basic test case - pound on a file system, drop power to the storage
> (and or server) and then on reboot, try to remount. Verification
> would be in the QA test case to unmount and fsck to make sure our
> journal was robust.

The original reason for the periodic fsck was not a fear that the
journalling system worked --- it was a concern that the hardware was
reliable.  (Ted's law of PC class hardware: it's crap. :-) That was
the reason for the periodic fsck in the BSD days, and it's the same
now.

That being said, I agree that 20-40 reboots (it's actually randomized
by mke2fs these days; the setting in libext2fs isn't the whole story)
is a ver y rough metric.  I'd much rather do the checking periodically
via snapshots in cron, at which point the reboot counter becomes moot
(the snapshot check zero's the mount count and sets the last checked
time correctly).

							- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists