qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: J M Cerqueira Esteves <jmce@artenumerica.com>
To: qemu-devel@nongnu.org
Cc: AN support <support@artenumerica.com>
Subject: Re: [Qemu-devel] QCOW image corruption under QEMU 0.9.0
Date: Sun, 25 Feb 2007 03:38:57 +0000	[thread overview]
Message-ID: <45E104D1.5090003@artenumerica.com> (raw)
In-Reply-To: <45E0FA97.3030103@artenumerica.com>

J M Cerqueira Esteves wrote:
> Curiously this damaged image file has 4543348736 bytes.
> I wonder if there some new bug triggered by the image file size,
> for some size around 4500000000 bytes...

I have a copy of the disk image file as it was just before starting the
qemu run which damaged it, and now I noticed that, during that qemu run,
the image file size did not change: 4543348736 bytes.

However, comparing both images with  cmp -l  shows extensive changes.
Just an example, from the first bytes (byte number, original value,
corrupted value):

         1 121   0
         2 106   0
         3 111   0
         4 373   0
         8   2   0
        24  14   0
        28   5   0
        39  50   0
        47  20   0
        52   1   0
        55  20   0
        60   2   0
      1881   0 200
      1887   0  40
      1889   0 200
      1895   0 100
      9049 200   0
      9054   1   0
      9055 220   0
      9057 200   0
      9061  60   0
      9062 115   0
      9063 100   0
... many more zeroed out...
     49487 220   0
     49569 200   0
     49573 325   0
     49574 357   0
     49575 300   0
     49665   0 147
     49666   0 145
     49667   0  55
     49668   0  62
     49669   0  56
     49670   0  66
     49671   0  56
     49672   0  61
     49673   0  70
     49674   0  55
     49675   0  63
     49676   0  55
     49677   0 153
 ... many more un-zeroed ...
     49853   0  40
     49854   0 151
     49855   0 163
     49856   0  40
     49857 200 141
     49858   0 166
     49859   0 141
     49860   0 151
     49861  46 154
     49862 174 141
     49863 140 142
     49864   0 154
     49865   0 145
 ... many more un-zeroed ...
     49983   0 142
     49984   0 157
     49985 200 157
     49986   0 164
     49987   0  40
     49988   0 171
     49989  15 157
     49990 354 165
     49991 200 162
     49992   0  40
     49993 200 155
     49994   0 141
     49995   0 143
     49996   0 150
     49997  16 151
     49998   1 156
     49999 260 145
     50000   0  56
     50001   0  12
     50002   0  12
    ...

Best regards
                                                     J Esteves

  reply	other threads:[~2007-02-25  3:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-23 13:18 [Qemu-devel] QCOW image corruption under QEMU 0.9.0 J M Cerqueira Esteves
2007-02-23 18:42 ` [Qemu-devel] " J M Cerqueira Esteves
2007-02-25  2:02 ` [Qemu-devel] MORE " AN support
2007-02-25  2:55 ` [Qemu-devel] " J M Cerqueira Esteves
2007-02-25  3:38   ` J M Cerqueira Esteves [this message]
2007-02-25  6:01   ` J M Cerqueira Esteves
2007-02-25  8:07     ` [Qemu-devel] QEMU with smp Danny Chieh-Yao, Cheng

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=45E104D1.5090003@artenumerica.com \
    --to=jmce@artenumerica.com \
    --cc=qemu-devel@nongnu.org \
    --cc=support@artenumerica.com \
    /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;
as well as URLs for NNTP newsgroup(s).