WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] xvda I/O errors in linux 3.1 under XCP 1.0

To: George Shuklin <george.shuklin@xxxxxxxxx>
Subject: Re: [Xen-users] xvda I/O errors in linux 3.1 under XCP 1.0
From: Mike McClurg <mike.mcclurg@xxxxxxxxxx>
Date: Fri, 30 Sep 2011 11:36:23 +0100
Cc: "xen-users@xxxxxxxxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 30 Sep 2011 03:38:02 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1317314618.14194.13.camel@mabase>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <1317314618.14194.13.camel@mabase>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; Linux i686; rv:7.0) Gecko/20110923 Thunderbird/7.0
On 29/09/11 17:43, George Shuklin wrote:
> Good day.
>
> I'm getting this error:
>
> [101017.440858] blkfront: barrier: empty write xvda op failed
> [101017.440862] blkfront: xvda: barrier or flush: disabled
> [101017.463438] end_request: I/O error, dev xvda, sector 3676376
> [101017.463452] end_request: I/O error, dev xvda, sector 3676376
> [101017.463459] Buffer I/O error on device xvda1, logical block 459291
> [101017.463464] lost page write due to I/O error on xvda1
>
> It happens in every linux 3.1 rc since rc2 during boot (may be in
> 3.1-rc1 - but it crash at start). Linux 3.0 boots fine. This is not
> hardware or storage error: only Linux 3.1 cause this.
>
> Did some one saw this?  What the reason can be behind this? (I'm not
> sure but this looks like announcing wrong size of block device, so ext3
> failing to change it journal).

That sounds like more of a linux bug to me. I think that it might be
better to report this to either the linux kernel mailing list, or
possibly the xen-devel mailing list (the list for discussing hypervisor
development). I'd check those lists first before posting, in case
someone has already reported this.

Mike

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

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