From: Eric Sandeen <sandeen@sandeen.net>
To: Gerard Beekmans <GBeekmans@tsag.net>,
"xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: Unable to mount and repair filesystems
Date: Thu, 29 Jan 2015 14:18:14 -0600 [thread overview]
Message-ID: <54CA9586.1010607@sandeen.net> (raw)
In-Reply-To: <D90435AEFF34654AA1122988C66C8678023F0277C9@exchange.tsag.local>
On 1/29/15 11:36 AM, Gerard Beekmans wrote:
> Hi,
>
> One of our VMware VMs crashed which has resulted in a few XFS filesystems unable to mount and be repaired.
>
> Some VM details:
> - Distribution is CentOS 7
> - Partitions reside inside LVM
> - Tried CentOS provided xfsprogs-3.2.0-alpha2 as well as manually compiling 3.2.2
>
> When attempting to mount:
>
> [71895.922382] XFS (dm-9): Mounting Filesystem
> [71895.994614] XFS (dm-9): Starting recovery (logdev: internal)
> [71896.000910] XFS (dm-9): Metadata corruption detected at xfs_agf_read_verify+0x70/0x120 [xfs], block 0x753001
> [71896.002304] XFS (dm-9): Unmount and run xfs_repair
> [71896.003649] XFS (dm-9): First 64 bytes of corrupted metadata buffer:
> [71896.005049] ffff8800b1200c00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> [71896.006468] ffff8800b1200c10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> [71896.007799] ffff8800b1200c20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> [71896.009116] ffff8800b1200c30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
all zeros...
> [71896.010482] XFS (dm-9): metadata I/O error: block 0x753001 ("xfs_trans_read_buf_map") error 117 numblks 1
> mount: mount /dev/mapper/data-srv on /srv failed: Structure needs cleaning
>
>
> xfs_repair:
>
> xfs_repair /dev/mapper/data-srv
> Phase 1 - find and verify superblock...
> couldn't verify primary superblock - bad magic number !!!
bad first block, too.
Are you certain that the volume / storage behind dm-9 is in decent shape? (i.e. is it really even an xfs filesystem?)
A VM crashing definitely should not result in a badly corrupt/unmountable filesystem.
Is there any other interesting part of the story? :)
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-01-29 20:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-29 17:36 Unable to mount and repair filesystems Gerard Beekmans
2015-01-29 20:18 ` Eric Sandeen [this message]
2015-01-29 21:27 ` Gerard Beekmans
2015-01-29 21:49 ` Eric Sandeen
2015-01-29 21:59 ` Gerard Beekmans
2015-01-29 22:15 ` Eric Sandeen
2015-01-29 23:12 ` Dave Chinner
2015-01-30 0:04 ` Gerard Beekmans
2015-01-29 22:57 ` Dave Chinner
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=54CA9586.1010607@sandeen.net \
--to=sandeen@sandeen.net \
--cc=GBeekmans@tsag.net \
--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