public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Markus Trippelsdorf <markus@trippelsdorf.de>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: xfs_repair refuses to run on cleanly mountable partition
Date: Mon, 07 Oct 2013 10:21:56 -0500	[thread overview]
Message-ID: <5252D194.1010609@sandeen.net> (raw)
In-Reply-To: <20131007151637.GA280@x4>

On 10/7/13 10:16 AM, Markus Trippelsdorf wrote:
> x4 ~ # xfs_repair -V
> xfs_repair version 3.2.0-alpha1
> 
> x4 ~ # mount -o logbsize=256k /dev/sdc1 /mnt
> ...
> [ 6419.592649] XFS (sdc1): Mounting Filesystem
> [ 6419.642480] XFS (sdc1): Ending clean mount
> 
> x4 ~ # xfs_info /dev/sdc1
> meta-data=/dev/sdc1              isize=256    agcount=4, agsize=61047552 blks
>          =                       sectsz=4096  attr=2, projid32bit=0
>          =                       crc=0
> data     =                       bsize=4096   blocks=244190208, imaxpct=25
>          =                       sunit=0      swidth=0 blks
> naming   =version 2              bsize=4096   ascii-ci=0
> log      =internal               bsize=4096   blocks=119233, version=2
>          =                       sectsz=4096  sunit=1 blks, lazy-count=1
> realtime =none                   extsz=4096   blocks=0, rtextents=0
> 
> x4 ~ # umount /mnt
> 
> x4 ~ # xfs_repair /dev/sdc1
> Phase 1 - find and verify superblock...
> Phase 2 - using internal log
>         - zero log...
> ERROR: The filesystem has valuable metadata changes in a log which needs to
> be replayed.  Mount the filesystem to replay the log, and unmount it before
> re-running xfs_repair.  If you are unable to mount the filesystem, then use
> the -L option to destroy the log and attempt a repair.
> Note that destroying the log may cause corruption -- please attempt a mount
> of the filesystem before doing this.

What kernel are you running?  Does older xfs_repair behave differently?
(use xfs_repair -n if you test an old xfsprogs, to preserve this state
for debugging...)

Perhaps copying out or dumping the log w/ xfs_logprint would also help, 
maybe start with:

# xfs_logprint -t /dev/sdc1

-Eric

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2013-10-07 15:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-07 15:16 xfs_repair refuses to run on cleanly mountable partition Markus Trippelsdorf
2013-10-07 15:21 ` Eric Sandeen [this message]
2013-10-07 15:29   ` Markus Trippelsdorf
2013-10-07 15:36     ` Eric Sandeen
2013-10-07 15:40       ` Markus Trippelsdorf
2013-10-07 15:54         ` Eric Sandeen
2013-10-07 16:52           ` [bisected] " Markus Trippelsdorf
2013-10-07 17:12             ` Eric Sandeen
2013-10-07 17:25               ` Markus Trippelsdorf

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=5252D194.1010609@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=markus@trippelsdorf.de \
    --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