All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: John Snow <jsnow@redhat.com>
Cc: Vasiliy Tolstov <v.tolstov@selfip.ru>,
	qemu-devel <qemu-devel@nongnu.org>,
	Qemu-block <qemu-block@nongnu.org>
Subject: Re: [Qemu-devel] qemu 2.9.0 qcow2 file failed to open after hard server reset
Date: Fri, 22 Dec 2017 09:23:08 +0000	[thread overview]
Message-ID: <20171222092308.GF30605@redhat.com> (raw)
In-Reply-To: <56c5bcbb-02c0-a3f7-4363-e3141476b2f8@redhat.com>

On Thu, Dec 21, 2017 at 05:58:47PM -0500, John Snow wrote:
> 
> 
> On 12/21/2017 05:13 PM, Vasiliy Tolstov wrote:
> > Hi! Today my server have forced reboot and one of my vm can't start
> > with message:
> > qcow2: Marking image as corrupt: L2 table offset 0x3f786d6c207600
> > unaligned (L1 index: 0); further corruption events will be suppressed
> > 
> > i'm use debian jessie with hand builded qemu 2.9.0, i'm try to
> > qemu-img check but it not helps. How can i recover data inside qcow2
> > file? (i'm not use compression or encryption inside it).
> > 
> 
> Not looking good if you're missing the very first L2 table in its entirety.
> 
> You might be able to go through this thing by hand and learn for
> yourself where the L2 table is (it will be a 64KiB region, aligned to a
> 64KiB boundary, that all contain 64bit, 64KiB aligned pointers that will
> be less than the size of the file. the offset of this missing region is
> not likely to be referenced elsewhere in your file.)

Fun. That rather makes you wish that every single distinct type of table
in QCow2 files had a unique UUID value stored in it, to make forensics
like this easier :-)

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|

  reply	other threads:[~2017-12-22  9:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-21 22:13 [Qemu-devel] qemu 2.9.0 qcow2 file failed to open after hard server reset Vasiliy Tolstov
2017-12-21 22:58 ` John Snow
2017-12-22  9:23   ` Daniel P. Berrange [this message]
2017-12-27 21:46     ` Vasiliy Tolstov
2017-12-27 21:47   ` Vasiliy Tolstov
2018-01-10 15:46     ` John Snow

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=20171222092308.GF30605@redhat.com \
    --to=berrange@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=v.tolstov@selfip.ru \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.