From: "Niccolò Belli" <darkbasic@linuxsystems.it>
To: xfs@oss.sgi.com
Subject: How to recover data from an xfs partition
Date: Sat, 12 May 2012 19:28:31 +0200 [thread overview]
Message-ID: <4FAE9DBF.1090505@linuxsystems.it> (raw)
Hi,
I had a (software) problem with my xen server ended ruining my domU
partitions. I already recovered all my ext4 partitions using fsck.ext4,
but I can't recover the only xfs partition I have :(
When I try to mount I get:
root@firewall:~# mount -o loop,offset=$((97280*1024)) -t xfs
/srv/xen/webserver.img /mnt
mount: Structure needs cleaning
While when trying to fsck I get:
root@firewall:~# xfs_check /dev/loop51
xfs_check: /dev/loop51 is not a valid XFS filesystem (unexpected SB
magic number 0xeb639010)
xfs_check: size check failed
xfs_check: WARNING - filesystem uses v1 dirs,limited functionality provided.
cache_node_purge: refcount was 1, not zero (node=0x11f0820)
xfs_check: cannot read root inode (22)
cache_node_purge: refcount was 1, not zero (node=0x11f0970)
xfs_check: cannot read realtime bitmap inode (22)
xfs_check: size check failed
xfs_check: WARNING - filesystem uses v1 dirs,limited functionality provided.
bad superblock magic number eb639010, giving up
xfs_check:
root@firewall:~# xfs_check /dev/loop51
xfs_check: /dev/loop51 is not a valid XFS filesystem (unexpected SB
magic number 0xeb639010)
xfs_check: size check failed
xfs_check: WARNING - filesystem uses v1 dirs,limited functionality provided.
cache_node_purge: refcount was 1, not zero (node=0x22f1820)
xfs_check: cannot read root inode (22)
cache_node_purge: refcount was 1, not zero (node=0x22f1970)
xfs_check: cannot read realtime bitmap inode (22)
xfs_check: size check failed
xfs_check: WARNING - filesystem uses v1 dirs,limited functionality provided.
bad superblock magic number eb639010, giving up
xfs_repair:
root@firewall:~# xfs_repair /dev/loop51
Phase 1 - find and verify superblock...
bad primary superblock - bad magic number !!!
attempting to find secondary superblock...
................................................................................found
candidate secondary superblock...
unable to verify superblock, continuing...
.............
[...]
....................................Sorry, could not find valid
secondary superblock
Exiting now.
How can I restore my data? I cannot believe I had no problems restoring
*15* ext4 partitions while I can't restore the only xfs partition I have :(
Hope you can help,
Niccolò
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2012-05-12 17:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-12 17:28 Niccolò Belli [this message]
2012-05-18 14:31 ` How to recover data from an xfs partition 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
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=4FAE9DBF.1090505@linuxsystems.it \
--to=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 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.