From: Dave Chinner <david@fromorbit.com>
To: Roy Zhang <royzhangzzl@gmail.com>
Cc: xfs-masters <xfs-masters@oss.sgi.com>, xfs <xfs@oss.sgi.com>
Subject: Re: [xfs-masters] xfs corruption - structure need cleaning
Date: Wed, 16 Oct 2013 07:43:46 +1100 [thread overview]
Message-ID: <20131015204346.GS4446@dastard> (raw)
In-Reply-To: <CAMg3XqqJgxnc2+ZkuMaK9RC1_Basfh9AzcqCpNdvmPpCXgNHZg@mail.gmail.com>
On Tue, Oct 15, 2013 at 09:45:27PM +0800, Roy Zhang wrote:
> Hi,
> I met a problem that cannot mount xfs, log as below.
> I got know xfs_repair -L will fix this situation, I want to know how
> and why cause it, it's a bug in xfs or hdd? Is there any patch to fix
> it?
>
> Thanks
> Roy
>
> Oct 9 18:26:52 mcluster-alpha-node3 kernel: [11840.232985] XFS
> (dm-3): Mounting Filesystem
> Oct 9 18:26:52 mcluster-alpha-node3 kernel: [11840.327773] XFS
> (dm-3): Internal error xlog_clear_stale_blocks(2) at line 1353 of file
> fs/xfs/xfs_log_recover.c. Caller 0xffffffffa01f894d
The head and tail of the log are confused - different cycle numbers
but the tail is behind the head. That implies that there are 3 cycle
numbers visible in the log, when here should only be 2, which would
mean that some log write did not make it to disk correctly.
You'll need to provide a copy of the log (xfs_logprint can get that
for you) and the information about your system described here:
http://xfs.org/index.php/XFS_FAQ#Q:_What_information_should_I_include_when_reporting_a_problem.3F
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-10-15 20:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-15 13:45 xfs corruption - structure need cleaning Roy Zhang
2013-10-15 13:54 ` Carlos Maiolino
2013-10-15 20:43 ` Dave Chinner [this message]
[not found] ` <CAMg3XqptephuOPEJ-iiQF+Bs5Kp7MO=D-siw6fbNMG4=2CQGKg@mail.gmail.com>
2013-10-16 1:46 ` [xfs-masters] " 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=20131015204346.GS4446@dastard \
--to=david@fromorbit.com \
--cc=royzhangzzl@gmail.com \
--cc=xfs-masters@oss.sgi.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.