From: Dave Chinner <david@fromorbit.com>
To: Rafael Weingartner <rafaelweingartner@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: XFS_REPAIR on LVM partition
Date: Thu, 19 Dec 2013 08:34:34 +1100 [thread overview]
Message-ID: <20131218213434.GK31386@dastard> (raw)
In-Reply-To: <CAG97raf7Na5UwzREJ_C9nYJ64r7PPwkhp_qcPiGVnKqu+ujAgw@mail.gmail.com>
[ cc'd the XFS list again - please keep problem triage on the public
lists so that more than one person can help you. ]
On Mon, Dec 16, 2013 at 02:53:03PM -0200, Rafael Weingartner wrote:
> Today, I let the command xfs_repair /dev/... ran till it finished, I got
> the following messages:
>
> Phase 1 - Find and verify superblock ....
> > Could not verify primary superblock - not enough secondary superblocks
> > with matching geometry!!
The primary superblock dump looked valid, but it it couldn't find
matching secondary superblocks from the contents of the primary that
it found.
> > attempting to find a secondary superblock.....
> > ...
> > ..
> > ...
> > ...
> > found candidate secondary superblock....
> > unable to verify superblock, continuing....
And it found blocks with the correct superbloc magic numbers, but
they don't match the primary superblock that was found.
> > found candidate secondary superblock....
> > unable to verify superblock, continuing...
> > ...
> > ...
> > ..............................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................Sorry,
> > could not find valid secondary superblock
> > Exiting now.
>
>
> Should I upgrade the xfsprogs and try to run the xfs_repair again?
> Or does that message mean that there is no way of recovering the filesystem?
It's still possible to recover, but more info is needed first.
Can you get xfs_db to dump the primary and a couple of secondary
superblocks?
# xfs_db -c "sb 0" -c p -c "sb 2" -c p -c "sb 7" -c p <dev>
And post the output?
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-12-18 21:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-15 22:47 XFS_REPAIR on LVM partition Rafael Weingartner
2013-12-16 0:01 ` Dave Chinner
2013-12-16 0:34 ` Rafael Weingartner
2013-12-16 3:05 ` Dave Chinner
2013-12-16 8:52 ` Rafael Weingartner
2013-12-16 12:54 ` Dave Chinner
[not found] ` <CAG97raeP-0QEhhYjDX_DDxzS3TN_brRSU6G+j-+V3KEuJ7Ym6Q@mail.gmail.com>
[not found] ` <CAG97raf7Na5UwzREJ_C9nYJ64r7PPwkhp_qcPiGVnKqu+ujAgw@mail.gmail.com>
2013-12-18 21:34 ` Dave Chinner [this message]
2013-12-18 23:29 ` Rafael Weingartner
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=20131218213434.GK31386@dastard \
--to=david@fromorbit.com \
--cc=rafaelweingartner@gmail.com \
--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.