public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frans Pop <elendil@planet.nl>
To: Massimo Cetra <mcetra@navynet.it>
Cc: linux-kernel@vger.kernel.org, Mark McLoughlin <markmc@redhat.com>,
	Rusty Russell <rusty@rustcorp.com.au>,
	Mikulas Patocka <mpatocka@redhat.com>,
	Alasdair G Kergon <agk@redhat.com>, Neil Brown <neilb@suse.de>,
	virtualization <virtualization@lists.linux-foundation.org>,
	dm-devel <dm-devel@redhat.com>
Subject: Re: Bug on barriers for virtio_blk device - end_request: I/O error, dev vda, sector 0
Date: Wed, 14 Oct 2009 22:32:12 +0200	[thread overview]
Message-ID: <200910142232.14837.elendil@planet.nl> (raw)
In-Reply-To: <4AD62690.9080408@navynet.it>

Added CCs for the author of and people CCed on the patch.

The patch has been submitted twice (6 Aug, 3 Sept), the first time there 
was one concern voiced which seems to have been addressed in replies. The 
second time there were no reactions.

The patch seems to work for Massimo...

Massimo Cetra wrote:
> Massimo Cetra ha scritto:
>> Hello all,
>>
>> i ended up with some thiusands of errors after upgrading to 2.6.31.2
>> like this one:
>>
>> end_request: I/O error, dev vda, sector 0
>> end_request: I/O error, dev vda, sector 0
>> end_request: I/O error, dev vda, sector 0
>> end_request: I/O error, dev vda, sector 0
>>
>> I am using ocfs2 on top of drbd on top of LVM in a KVM guest that uses
>> virtio_blk.
>>
>> The bug is already known, see here:
>> https://bugzilla.redhat.com/show_bug.cgi?id=514901
>>
>> A patch exists and the problem has already been submitted here in the
>> list.
>> See here: http://lkml.org/lkml/2009/8/6/153
>>
>> That fix is not in 2.6.31 nor in 2.6.32-RCX
>>
>> Could you please consider pulling it and adding this fix for inclusion
>> in 2.6.31.$next and also to mainline?
>>
>> Thanks.
>
> No one listening here ?

It helps if you CC the people who maintain the relevant code.

> This makes virtio_blk on LVM unusable.

Cheers,
FJP

  reply	other threads:[~2009-10-14 20:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-14 14:11 Bug on barriers for virtio_blk device - end_request: I/O error, dev vda, sector 0 Massimo Cetra
2009-10-14 19:29 ` Massimo Cetra
2009-10-14 20:32   ` Frans Pop [this message]
2009-10-15 10:55     ` Massimo Cetra
2009-10-15 11:12       ` NeilBrown

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=200910142232.14837.elendil@planet.nl \
    --to=elendil@planet.nl \
    --cc=agk@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markmc@redhat.com \
    --cc=mcetra@navynet.it \
    --cc=mpatocka@redhat.com \
    --cc=neilb@suse.de \
    --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