From: Joe Thornber <thornber@redhat.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: dm-devel@redhat.com, ejt@redhat.com
Subject: Re: dm-thinp bug
Date: Wed, 27 Apr 2011 10:23:40 +0100 [thread overview]
Message-ID: <1303896220.4679.54.camel@ubuntu> (raw)
In-Reply-To: <20110427083917.GA23330@infradead.org>
On Wed, 2011-04-27 at 04:39 -0400, Christoph Hellwig wrote:
> On Wed, Apr 27, 2011 at 09:27:37AM +0100, Joe Thornber wrote:
> > On Tue, 2011-04-26 at 14:47 -0400, Christoph Hellwig wrote:
> > > I can reproduce a bug in virtio triggered by running under dm-thinp by
> > > just copying lots of files from my home directory into a freshly created
> > > filesystem on dm-thinp.
> >
> > Finally someone has tried using it! I'll look into this today.
>
> I actually used the earlier version you posted and didn't reproduce it
> there. I have a gut feeling it's related to barriers, as I probably
> just did a basic ext3 test back then.
I hope this isn't the case.
>
> One thing that springs to mind is that both the thinp and multisnap
> targets don't appear to support empty barriers (that is REQ_FLUSH
> without a payload), because they don't set ti->num_flush_requests, but
> I'm not sure that's related.
Fixed in thinp and multisnap public repos.
- Joe
next prev parent reply other threads:[~2011-04-27 9:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-26 18:47 dm-thinp bug Christoph Hellwig
2011-04-27 8:27 ` Joe Thornber
2011-04-27 8:39 ` Christoph Hellwig
2011-04-27 9:23 ` Joe Thornber [this message]
2011-04-27 9:08 ` Joe Thornber
2011-04-27 9:32 ` Christoph Hellwig
2011-04-27 9:52 ` Joe Thornber
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=1303896220.4679.54.camel@ubuntu \
--to=thornber@redhat.com \
--cc=dm-devel@redhat.com \
--cc=ejt@redhat.com \
--cc=hch@infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.