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

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

To: James Harper <james.harper@xxxxxxxxxxxxxxxx>, <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] Re: [Xen-devel] Any known block device corruption problems in 3.1.0 upto release?
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Fri, 01 Jun 2007 09:32:33 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 01 Jun 2007 01:30:14 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <AEC6C66638C05B468B556EA548C1A77D01166908@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>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acej9pJOFjEXA1grRAG1eqoZygIVUQAIQsXwAAPyOXY=
Thread-topic: [Xen-devel] Any known block device corruption problems in 3.1.0 upto release?
User-agent: Microsoft-Entourage/11.3.3.061214


On 1/6/07 07:42, "James Harper" <james.harper@xxxxxxxxxxxxxxxx> wrote:

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

If you did an unclean shutdown of the guest, and/or qemu-dm crashed then
that could easily explain small-scale block-device corruption. So the
question is: what events originally caused the unclean shutdown?

 -- Keir



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

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