[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.2.00.1011191640320.3238@dhcp-lab-213.englab.brq.redhat.com>
Date: Fri, 19 Nov 2010 16:44:33 +0100 (CET)
From: Lukas Czerner <lczerner@...hat.com>
To: Mark Lord <kernel@...savvy.com>
cc: "Ted Ts'o" <tytso@....edu>,
Steven Whitehouse <swhiteho@...hat.com>,
Lukas Czerner <lczerner@...hat.com>,
James Bottomley <James.Bottomley@...e.de>,
Christoph Hellwig <hch@...radead.org>,
Matthew Wilcox <matthew@....cx>,
Josef Bacik <josef@...hat.com>, linux-ext4@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
sandeen@...hat.com
Subject: Re: [PATCH 1/2] fs: Do not dispatch FITRIM through separate
super_operation
On Fri, 19 Nov 2010, Mark Lord wrote:
> On 10-11-19 09:02 AM, Ted Ts'o wrote:
> > but that's why mount -o discard is not the default.
>
>
> But, oddly, it _is_ the default for mke2fs -t ext4,
> which really threw me for a loop recently.
>
> I though my system had locked up when suddenly everything
> went dead for a very long time (many minutes) while installing a new system.
>
> Then I figured out what was going on.
> I really believe that "-K" should be the _default_ for mke2fs,
> as otherwise lots of other people probably also wonder
> if Linux is killing their SSD at system install time..
>
> Cheers
>
That is exactly a reason why I posted a patch for
"Make blkdev_issue_discard() interruptible", but nobody seems to care. As
an addition I have patched mke2fs to inform user about ongoing discard,
also with not much attention (Ted?).
Thanks!
-Lukas
--
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