[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] Any known block device corruption problems in 3.1.0 up to release?

  • To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
  • Date: Fri, 1 Jun 2007 12:43:01 +1000
  • Delivery-date: Thu, 31 May 2007 19:41:18 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: Acej9pJOFjEXA1grRAG1eqoZygIVUQ==
  • Thread-topic: Any known block device corruption problems in 3.1.0 up to release?

I've just had a virtual windows small business server that I was testing
suddenly refuse to boot (black screen almost immediately). It was
apparently working fine and then suddenly wouldn't boot. When I boot
from the CD into the windows recovery console, chkdsk tells me "The
volume appears to contain one or more unrecoverable problems", and no
more information than that. It looks like I can see the files on the
harddisk, but when I try to create a directory or something I get
"access denied".

It seems that some sort of fairly major block device corruption has
occurred, which isn't a good result for the testing I'm doing.

I did notice that something seemed to segfault and then I couldn't
connect via VNC at about the time the corruption would have occurred...

I'm using a version of Xen which I think slightly pre-dates the 3.1.0
release, on an AMD64 system which has not shown any other indication of
problems apart from this one incidence of corruption.

Are there any known block device corruption issues slightly before the
3.1.0 release that have been subsequently fixed? I guess it's worth
building a newer version, but I'd like to know that there was definitely
a known problem and it's definitely fixed...



Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.