linux-ext4 - Re: mkfs.ext4 vs. e2fsck discard oddities

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] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 1 Mar 2012 09:38:34 -0500
From:	Ted Ts'o <tytso@....edu>
To:	Lukas Czerner <lczerner@...hat.com>
Cc:	Eric Sandeen <sandeen@...hat.com>,
	ext4 development <linux-ext4@...r.kernel.org>
Subject: Re: mkfs.ext4 vs. e2fsck discard oddities

On Thu, Mar 01, 2012 at 08:12:44AM +0100, Lukas Czerner wrote:
> 
> actually mke2fs does discard block by default. It has been like that
> since the beginning. Back then we only had '-K' argument to 'keep'
> blocks and do not attempt to discard. Nowadays user can do '-E
> nodiscard', but it is users choice.

Ah, you're right.  The defaults had changed back and forth a couple of
times over time and I had lost track of how things had been settled
for mke2fs (which is different from e2fsck).  At least at one point it
was _not_ the default, and in fact the man page was out of sync with
the behavior of the mke2fs.

The point remains the same, though, if the file system was created
with mke2fs -E nodiscard, how do you undo that decision if there's no
way to force the discard of BLOCK_UNINIT blocks?

						- 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