public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
* Re: question about xfs/098
       [not found] <57BD507C.6050204@cn.fujitsu.com>
@ 2016-08-24 23:06 ` Darrick J. Wong
  0 siblings, 0 replies; only message in thread
From: Darrick J. Wong @ 2016-08-24 23:06 UTC (permalink / raw)
  To: Xiao Yang; +Cc: fstests

[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
> 
> 
> 
> 

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2016-08-24 23:07 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [not found] <57BD507C.6050204@cn.fujitsu.com>
2016-08-24 23:06 ` question about xfs/098 Darrick J. Wong

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox