All of lore.kernel.org
 help / color / mirror / Atom feed
From: Massimo Cetra <mcetra@navynet.it>
To: linux-kernel@vger.kernel.org
Subject: Bug on barriers for virtio_blk device - end_request: I/O error, dev vda, sector 0
Date: Wed, 14 Oct 2009 16:11:41 +0200	[thread overview]
Message-ID: <4AD5DC1D.9070002@navynet.it> (raw)

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.


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

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

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=4AD5DC1D.9070002@navynet.it \
    --to=mcetra@navynet.it \
    --cc=linux-kernel@vger.kernel.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.