public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Xiao Yang <yangx.jy@cn.fujitsu.com>
Cc: fstests@vger.kernel.org
Subject: Re: question about xfs/098
Date: Wed, 24 Aug 2016 16:06:20 -0700	[thread overview]
Message-ID: <20160824230620.GE8265@birch.djwong.org> (raw)
In-Reply-To: <57BD507C.6050204@cn.fujitsu.com>

[cc list]

On Wed, Aug 24, 2016 at 03:45:00PM +0800, Xiao Yang wrote:
> Hi Darrick
> 
> When i run xfstests test case xfs/098 on RHEL7.3Alpha with xfsprog-dev(4.5.0),
> I always get following error:
> ------------------------------------------------------------------
> + repair fs
> Phase 1 - find and verify superblock...
> Phase 2 - using internal log
>         - zero log...
> Log inconsistent (didn't find previous header)
> failed to find log head
> zero_log: cannot find log head/tail (xlog_find_tail=5)
> 
> fatal error -- ERROR: The log head and/or tail cannot be discovered. Attempt to mount the
> filesystem to replay the log or use the -L option to destroy the log and
> ------------------------------------------------------------------
> 
> When metadata is changed by corrupting the journal, xfs_repair fails
> to repair corrupt xfs filesystem.  I'd like to know this is expected
> behavior for xfs_repair?  Can we use -L option to repair corrupt xfs
> filesystem successfully.

xfs_repair is not capable of replaying the journal at all.  The only
option is to try to mount the fs, and if that fails, xfs_repair -L
will zero the log and check the filesystem.

So yes, that is the expected behavior.

--D

> 
> Please advise. Thanks very much.
> 
> Regards,
> Xiao Yang
> 
> 
> 
> 

           reply	other threads:[~2016-08-24 23:07 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <57BD507C.6050204@cn.fujitsu.com>]

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=20160824230620.GE8265@birch.djwong.org \
    --to=darrick.wong@oracle.com \
    --cc=fstests@vger.kernel.org \
    --cc=yangx.jy@cn.fujitsu.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