From: Ted Ts'o <tytso@mit.edu>
To: Lukas Czerner <lczerner@redhat.com>
Cc: Eric Sandeen <sandeen@redhat.com>,
ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: mkfs.ext4 vs. e2fsck discard oddities
Date: Thu, 1 Mar 2012 09:38:34 -0500 [thread overview]
Message-ID: <20120301143834.GA30578@thunk.org> (raw)
In-Reply-To: <alpine.LFD.2.00.1203010804410.6491@dhcp-27-109.brq.redhat.com>
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
next prev parent reply other threads:[~2012-03-01 14:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 17:34 mkfs.ext4 vs. e2fsck discard oddities Eric Sandeen
2012-02-29 7:12 ` Lukas Czerner
2012-02-29 16:01 ` Eric Sandeen
2012-03-01 4:47 ` Theodore Tso
2012-03-01 7:12 ` Lukas Czerner
2012-03-01 14:38 ` Ted Ts'o [this message]
2012-03-01 14:54 ` Lukas Czerner
2012-03-08 16:48 ` Phillip Susi
2012-03-09 8:59 ` Lukas Czerner
2012-03-09 15:14 ` Phillip Susi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120301143834.GA30578@thunk.org \
--to=tytso@mit.edu \
--cc=lczerner@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).