public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: "SourceForge.net" <noreply@sourceforge.net>
To: noreply@sourceforge.net
Subject: [ kvm-Bugs-2490866 ] repeatable corruption with qcow2 on kvm-79
Date: Tue, 06 Jan 2009 21:10:49 +0000	[thread overview]
Message-ID: <E1LKJCL-0005AK-91@d55xhf1.ch3.sourceforge.com> (raw)

Bugs item #2490866, was opened at 2009-01-06 21:10
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2490866&group_id=180599

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: qemu
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Adrian Bridgett (abridgett)
Assigned to: Nobody/Anonymous (nobody)
Summary: repeatable corruption with qcow2 on kvm-79

Initial Comment:
Creating a qcow2 image, mkfs.ext3, sometimes mounting it would fail immediately, but in all cases it would corrupt (overwritten with zeros) after starting up backuppc on it.   This is KVM-79 on a Debian lenny host and guest.

This occured using virtio or not.  Swapping to a raw file or LV worked flawlessly.  I've tested the box with memtest and I don't have issues elsewhere but I've seen corruptions on other images.  host and guest are both 2.6.26-1-adm64 kernel (debian lenny) I'm running 32-bit userspace everywhere.  Dual core Intel Core2 E6300.

I see KVM-81 has "improve qcow2 data integrity with cache=writethrough" which _might_ be what I'm hitting - but I can't find more details about this to check (and backport patch to debian package or wait for newer debian package).

thanks.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2490866&group_id=180599

             reply	other threads:[~2009-01-06 21:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-06 21:10 SourceForge.net [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-01-07  7:42 [ kvm-Bugs-2490866 ] repeatable corruption with qcow2 on kvm-79 SourceForge.net
2009-01-07 17:14 SourceForge.net
2009-01-13  7:48 SourceForge.net
2009-01-13  8:23 SourceForge.net
2009-01-13 10:23 SourceForge.net
2009-01-13 11:50 SourceForge.net
2009-01-15  1:47 SourceForge.net
2009-01-21  6:47 SourceForge.net
2009-01-24 14:17 SourceForge.net
2009-08-10 12:18 SourceForge.net
2009-08-25  2:20 SourceForge.net

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1LKJCL-0005AK-91@d55xhf1.ch3.sourceforge.com \
    --to=noreply@sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox