On 03/07/2010 05:00 PM, Christoph Hellwig wrote:
On Sun, Mar 07, 2010 at 12:32:38PM +0300, Michael Tokarev wrote:
Antoine Martin wrote:
[]
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2933400&group_id=180599
The initial report is almost 8 weeks old!
Is data-corruption and data loss somehow less important than the
hundreds of patches that have been submitted since?? Or is there a fix
somewhere I've missed?
I can only guess that the info collected so far is not sufficient to
understand what's going on: except of "I/O error writing block NNN"
we does not have anything at all. So it's impossible to know where
the problem is.
Actually it is, and the bug has been fixed long ago in:
commit e2a305fb13ff0f5cf6ff805555aaa90a5ed5954c
Author: Christoph Hellwig<hch@xxxxxx>
Date: Tue Jan 26 14:49:08 2010 +0100
block: avoid creating too large iovecs in multiwrite_merge
Hmmm.
Like most of you, I had assumed that the data corruption bug (which I
have also encountered on this raw partition as it is well over 1TB)
would be the same as the "cannot open drive" bug I have described above,
but unfortunately I still cannot use 0.12.3 with raw disks with this
patch applied.
This is the patch, right?:
http://www.mail-archive.com/qemu-devel@xxxxxxxxxx/msg24129.html
So there is something else at play. And just for the record:
1) kvm-88 works fine *with the exact same setup*
2) I've tried running as root
3) The raw disk mounts fine from the host.
So I *know* the problem is with kvm. I wouldn't post to the list without
triple checking that.
I have also just tested with another raw partition which is much smaller
(1GB) and the same thing still occurs: kvm-88 works and qemu-kvm-0.12.3
does not.
So I think that it is fair to assume that this new problem is unrelated
to the partition size.
I've asked for it be added to the -stable series but that hasn't
happened so far.
If "eating-your-data" doesn't make it to -stable, what does??
Even if it did, I would have thought this kind of bug should warrant a
big warning sign somewhere.
Antoine
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
