This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] Buffer I/O error on device nbd0

To: Peter <peter.spamcatcher@xxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Buffer I/O error on device nbd0
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Sun, 7 Aug 2005 09:44:05 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Sun, 07 Aug 2005 08:48:08 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <42F49690.9030908@xxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <42F49690.9030908@xxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

On 6 Aug 2005, at 11:53, Peter wrote:

I'm not sure what we are running in /etc/init.d that could be starting something that triggers this error. And I don't believe we see the same error when we use the same file system under UML (but that may be because we have different kernel options enabled).

Has there been any further thought as to what triggers these error messages? Or do you have any advice on what we can do to try and avoid them?

I think they appear during udev or lvm startup. It may be because we build NBD as part of domU configuration (although only as a module). If this is only happening on domU then it's worth trying to remove NBD support from kernel configuration and recompile.

 -- Keir

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>