From: Andrew Patterson <andrew.patterson@hp.com>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: Alasdair G Kergon <agk@redhat.com>,
Mark McLoughlin <markmc@redhat.com>,
device-mapper development <dm-devel@redhat.com>,
Jens Axboe <jens.axboe@oracle.com>,
Rusty Russell <rusty@rustcorp.com.au>,
linux-kernel <linux-kernel@vger.kernel.org>,
virtualization <virtualization@lists.linux-foundation.org>,
". troy.heber"@hp.com
Subject: Re: [dm-devel] [PATCH] block: silently error unsupported empty barriers too
Date: Wed, 28 Oct 2009 20:19:01 +0000 [thread overview]
Message-ID: <1256761141.5830.79.camel@grinch> (raw)
In-Reply-To: <Pine.LNX.4.64.0908062148060.8764@hs20-bc2-1.build.redhat.com>
On Thu, 2009-08-06 at 21:50 -0400, Mikulas Patocka wrote:
> On Thu, 6 Aug 2009, Alasdair G Kergon wrote:
>
> > On Thu, Aug 06, 2009 at 12:14:17PM +0100, Mark McLoughlin wrote:
> > > We should error all barriers, even empty barriers, on devices like
> > > virtio_blk which don't support them.
> >
> > Have you considered whether or not virtio_blk actually needs to
> > support empty barriers?
> >
> > Alasdair
>
> This is only for request-based drivers, where it is the responsibility of
> blk-core to translate barriers. I think the empty barrier request anyway
> in blk_do_ordered, but with an error message. So the patch changes it to
> discard it early and queitly. It seems ok.
>
> Mikulas
> --
This patch seems to have been dropped. I can reproduce the error using
the following:
1. Create an LVM logical volume on top of a cciss device (note that
the cciss driver does not support barriers)
2. Create an ext3 file system on top of the logical volume
3. Mount the file-system using -obarrier=1
4. Copy some files onto the file-system
5. Run sync (dm_flush is called)
If I apply the patch (with some munging), the
"end_request: I/O error, dev cciss/cXdY, sector 0"
messages go away.
This is not strictly a regression, given that the problem was introduced
in 2.6.31, but I think it should still be fixed for 2.6.32.
Andrew
--
Andrew Patterson
Hewlett-Packard
next prev parent reply other threads:[~2009-10-28 20:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-06 11:14 [PATCH] block: silently error unsupported empty barriers too Mark McLoughlin
2009-08-06 11:45 ` [dm-devel] " Alasdair G Kergon
2009-08-06 12:22 ` Christoph Hellwig
2009-08-07 1:50 ` Mikulas Patocka
2009-10-28 20:19 ` Andrew Patterson [this message]
2009-10-28 21:03 ` Mike Snitzer
2009-10-29 7:45 ` Jens Axboe
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=1256761141.5830.79.camel@grinch \
--to=andrew.patterson@hp.com \
--cc=". troy.heber"@hp.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markmc@redhat.com \
--cc=mpatocka@redhat.com \
--cc=rusty@rustcorp.com.au \
--cc=virtualization@lists.linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox