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-devel

[Xen-devel] Re: ext3 directory corruption under Xen

To: adam radford <aradford@xxxxxxxxx>
Subject: [Xen-devel] Re: ext3 directory corruption under Xen
From: "Christopher S. Aker" <caker@xxxxxxxxxxxx>
Date: Mon, 23 Jun 2008 15:53:37 -0400
Cc: xen devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx
Delivery-date: Mon, 23 Jun 2008 12:54:02 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <b1bc6a000806231213p162cea21y37ed9ec1d3bb39fd@xxxxxxxxxxxxxx>
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: <485FCC25.7090401@xxxxxxxxxxxx> <b1bc6a000806231213p162cea21y37ed9ec1d3bb39fd@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.14 (Macintosh/20080421)
adam radford wrote:
On Mon, Jun 23, 2008 at 9:15 AM, Christopher S. Aker <caker@xxxxxxxxxxxx> wrote:

It's happened on a number of different hosts, all of the same hardware and
software configuration (Xen 3.2 64bit, 32bit pae dom0, 32bit pae domUs.  LVM
backend with 3ware hardware RAID-1).
>
A driver patch for older kernels including XenServer-4.1 is available here:

http://www.3ware.com/KB/article.aspx?id=15243&cNode=6I1C6S

Thanks, but unfortunately, from that link:

"3ware 9000 series controllers are not affected by this issue."

... which is what we're using. This problem only appeared after rebooting these machines into Xen. Some of affected boxes even ran 2.6.18 (non Xen) for awhile without any problems.

-Chris


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

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