From: laurent+xfs@u-picardie.fr
To: xfs@oss.sgi.com
Subject: able to mount a fs, unable to repair it
Date: Thu, 23 Dec 2010 02:53:08 +0100 [thread overview]
Message-ID: <87r5d9uuez.fsf@ezri.u-picardie.fr> (raw)
Hi !
For a reason all my xfs FS got corrupted at the same time.
My setup is: xen host using lvm on top of soft raid6 on top of jbod
3ware connected sata disks.
Both the host and the VM fs got corrupted.
ATM host is using 2.6.32 (debian/squeeze), xfsprogs are 3.1.4
I've had 2 kinds of corruptions:
1) unable to mount the FS, been able to xfs_repair -L
2) able to mount the FS, xfs_check was reporting errors, unable to
xfs_repair the fs
For most of the FS, i've managed to either mkfs.xfs or xfs_repair then
rsync from the backup.
I'm left with my 1.5TB fs for which i also have a full backup, i'm
able to mount it (no kernel error or anything when
mounting it). xfs_check on this unmounted FS gives errors. xfs_repair
(after a long long time) is unable to find a suitable thingie to
repair the FS.
https://gist.github.com/752411 xfs_{db,check,repair,metadump} results.
(haven't checked the memory/disk usage when doing the metadump)
I can't really tell why all this happened in the first place.
Been having power supply issues some weeks ago, been upgrading from
lenny to squeeze, been playing with xen & lxc at the same, been doing
my xmas shopping a bit late ! :-)
I'd be curious to know how to repair the 1.5TB FS, any idea on what i
could do ?
TIA
--
Laurent
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2010-12-23 1:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-23 1:53 laurent+xfs [this message]
2010-12-23 4:04 ` able to mount a fs, unable to repair it Eric Sandeen
2010-12-23 17:35 ` Emmanuel Florac
2010-12-23 19:34 ` laurent+xfs
2010-12-23 21:44 ` Emmanuel Florac
-- strict thread matches above, loose matches on Subject: below --
2010-12-23 23:47 Richard Scobie
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=87r5d9uuez.fsf@ezri.u-picardie.fr \
--to=laurent+xfs@u-picardie.fr \
--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