From: Eric Sandeen <sandeen@sandeen.net>
To: "Niccolò Belli" <darkbasic@linuxsystems.it>
Cc: xfs@oss.sgi.com
Subject: Re: How to recover data from an xfs partition
Date: Fri, 18 May 2012 17:47:22 -0500 [thread overview]
Message-ID: <4FB6D17A.7070408@sandeen.net> (raw)
In-Reply-To: <4FB6B7AB.8030405@linuxsystems.it>
On 5/18/12 3:57 PM, Niccolò Belli wrote:
> Il 18/05/2012 19:46, Eric Sandeen ha scritto:
>> the file backing it - what was that stored on?
>
> It was a raw image created with dd and stored on an SSD (ext4). Some
> of the virtual machines were on traditional hard disks instead
> (ext4).
>
> Only the running virtual machines got damaged, the main filesystems
> are perfect.
>
>> What it was that did the scribbling
>
> Rebooting. A simple, stupid reboot after upgrading Xen. While
> rebooting the system I got some kind of kernel panic and I had to use
> magic sysrq keys (remount read-only, sync, reboot).
Well - somehow the first sector of the xfs image got junk written into it...
hard to say how that happened, but the magic number lives in the
first sector of the xfs image hosted on ext4, and it was junk post-reboot.
I have never seen xfs corrupt _itself_ this way. TBH I'd be as likely to
blame the SSD, as anything. But you also have to have all of the data
integrity bits set up properly all along the virt stack to survive
a panic or power loss w/o corruption after the fact.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-05-18 22:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-12 17:28 How to recover data from an xfs partition Niccolò Belli
2012-05-18 14:31 ` Ben Myers
2012-05-18 15:01 ` Niccolò Belli
2012-05-18 17:46 ` Eric Sandeen
2012-05-18 20:57 ` Niccolò Belli
2012-05-18 22:47 ` Eric Sandeen [this message]
2012-05-18 23:36 ` Niccolò Belli
2012-05-21 7:44 ` Michael Monnerie
2012-05-21 8:23 ` Niccolò Belli
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=4FB6D17A.7070408@sandeen.net \
--to=sandeen@sandeen.net \
--cc=darkbasic@linuxsystems.it \
--cc=xfs@oss.sgi.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