linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@redhat.com>
To: Dave Chinner <david@fromorbit.com>
Cc: Spelic <spelic@shiftmail.org>,
	device-mapper development <dm-devel@redhat.com>,
	linux-ext4@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: Ext4 and xfs problems in dm-thin on allocation and discard
Date: Mon, 18 Jun 2012 23:12:42 -0400	[thread overview]
Message-ID: <20120619031241.GA3884@redhat.com> (raw)
In-Reply-To: <20120619015745.GJ25389@dastard>

On Mon, Jun 18 2012 at  9:57pm -0400,
Dave Chinner <david@fromorbit.com> wrote:

> On Mon, Jun 18, 2012 at 11:33:50PM +0200, Spelic wrote:
>
> > Please note that since I am above MD raid5 (I believe this is the
> > reason), the passdown of discards does not work, as my dmesg says:
> > [160508.497879] device-mapper: thin: Discard unsupported by data
> > device (dm-1): Disabling discard passdown.
> > but AFAIU, unless there is a thinp bug, this should not affect the
> > unmapping of thin blocks by fstrimming xfs... and in fact ext4 is
> > able to do that.
> 
> Does ext4 report that same error?

That message says the underlying device doesn't support discards
(because it is an MD device).  But the thinp device still has discards
enabled -- it just won't pass the discards down to the underlying data
device.

So yes, it'll happen with ext4 -- it is generated when the thin-pool
device is loaded (which happens independent of the filesystem that is
layered ontop).

The discards still inform the thin-pool that the corresponding extents
are no longer allocated.

  reply	other threads:[~2012-06-19  3:12 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-18 21:33 Ext4 and xfs problems in dm-thin on allocation and discard Spelic
2012-06-19  1:57 ` Dave Chinner
2012-06-19  3:12   ` Mike Snitzer [this message]
2012-06-19  6:32     ` Lukáš Czerner
2012-06-19 11:29       ` Spelic
2012-06-19 12:20         ` Lukáš Czerner
2012-06-19 13:34         ` Mike Snitzer
2012-06-19 13:16       ` Mike Snitzer
2012-06-19 13:25         ` Lukáš Czerner
2012-06-19 13:30           ` Mike Snitzer
2012-06-19 13:52             ` Spelic
2012-06-19 14:05               ` Eric Sandeen
2012-06-19 14:44               ` Mike Snitzer
2012-06-19 18:48                 ` Mike Snitzer
2012-06-19 20:06                   ` Dave Chinner
2012-06-19 20:21                     ` Ted Ts'o
2012-06-19 20:39                       ` Dave Chinner
2012-06-20  9:01                         ` Christoph Hellwig
2012-06-19 21:37                     ` Spelic
2012-06-19 23:12                       ` Dave Chinner
2012-06-20 12:11   ` Spelic
2012-06-20 22:53     ` Dave Chinner
2012-06-21 17:47       ` Mike Snitzer
2012-06-21 23:29         ` Dave Chinner
2012-07-01 14:53         ` Paolo Bonzini
2012-07-02 13:00           ` Mike Snitzer
2012-07-02 13:15             ` Paolo Bonzini
2012-06-19 14:09 ` Lukáš Czerner
2012-06-19 14:19   ` Ted Ts'o
2012-06-19 14:23     ` Eric Sandeen
2012-06-19 14:37     ` Lukáš Czerner
2012-06-19 14:43     ` [dm-devel] " Alasdair G Kergon
2012-06-19 15:28       ` Mike Snitzer
2012-06-19 16:03         ` [dm-devel] " Alasdair G Kergon
2012-06-19 19:58         ` Ted Ts'o
2012-06-19 20:44           ` Mike Snitzer

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=20120619031241.GA3884@redhat.com \
    --to=snitzer@redhat.com \
    --cc=david@fromorbit.com \
    --cc=dm-devel@redhat.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=spelic@shiftmail.org \
    --cc=xfs@oss.sgi.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).