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

["James Harper" <james.harper@xxxxxxxxxxxxxxxx>]

I believe it was qemu, as I accidentally purged all my
qemu-dm.[0-9]+.log files, and now can't find any record of it.

As per a more recent follow up message, while the corruption was enough
to stop windows booting, and the recovery console couldn't fix it,
running chkdsk from another domain fixed the problem in about 30
seconds, and there appears to be no actual lost data. So I'm guessing
that the problem was limited to a single cluster (or whatever NTFS calls
it's allocation units).

Thanks

James

> -----Original Message-----
> From: Keir Fraser [mailto:Keir.Fraser@xxxxxxxxxxxx]
> Sent: Friday, 1 June 2007 18:17
> To: James Harper; xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-devel] Any known block device corruption problems in
> 3.1.0 up to release?
> 
> What type of block-device backend were you using? Since it's a Windows
> guest
> presumably there are no PV drivers involved? Was the process that
crashed
> qemu-dm?
> 
>  -- Keir
> 
> On 1/6/07 03:43, "James Harper" <james.harper@xxxxxxxxxxxxxxxx> wrote:
> 
> > 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...
> >
> > Thanks
> >
> > James
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-devel
> 


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