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


[Xen-users] RE: [Xen-devel] Any known block device corruption problems i

To: <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] RE: [Xen-devel] Any known block device corruption problems in 3.1.0 upto release?
From: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
Date: Fri, 1 Jun 2007 16:42:40 +1000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 31 May 2007 23:41:09 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <AEC6C66638C05B468B556EA548C1A77D011668F4@trantor>
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/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <AEC6C66638C05B468B556EA548C1A77D011668F4@trantor>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acej9pJOFjEXA1grRAG1eqoZygIVUQAIQsXw
Thread-topic: [Xen-devel] Any known block device corruption problems in 3.1.0 upto release?
Oops... I meant to post this to xen-users.

I have gotten the server back up and running again by making the disk
accessible to another DomU and running a chkdsk on it that way. It found
a single corrupt index, repaired it, and everything is now fine. The
corruption was probably limited to a single block, and may have just
been caused by me shutting down the domain at exactly the wrong moment.

Can anyone comment on what write-back caching might be going on that
could cause these sorts of problems?



Xen-users mailing list

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