From: David Chinner <dgc@sgi.com>
To: Michael Nishimoto <miken@agami.com>
Cc: XFS Mailing List <xfs@oss.sgi.com>
Subject: Re: inconsistent xfs log record
Date: Wed, 9 Apr 2008 01:50:43 +1000 [thread overview]
Message-ID: <20080408155043.GZ108924158@sgi.com> (raw)
In-Reply-To: <47FAD04D.5080308@agami.com>
On Mon, Apr 07, 2008 at 06:54:21PM -0700, Michael Nishimoto wrote:
> I've just finished analyzing an xfs filesystem which won't recover.
> An inconsistent log record has 332 log operations but the num_logop field
> in the record header says 333 log operations. The result is that xfs
> recovery
> complains with "bad clientid" because recovery eventually attempts to decode
> garbage.
>
> The log record really has 332 log ops (I counted!).
>
> Looking through xlog_write(), I don't see any way that record_cnt can be
> bumped
> without also writing out a log operation.
Yeah, i remember going through this a while back tracking done the same
error on snapshot images (was a freeze problem) and I couldn't see how
it would happen, either.
Still, it's a single bit error so that's always suspicious - can you
reproduce this error reliably?
> Does this issue ring a bell with anyone?
FWIW, I have had 2-3 failures with a "bad clientid" on a 64k page size ia64
box since I switched from 16k page size about a month ago. I haven't seen any
consistent pattern to the failure yet, nor had a chance to perform any
sort of triage on the problem so I can't say whether I'm seeing the same
issue...
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
next prev parent reply other threads:[~2008-04-08 15:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-08 1:54 inconsistent xfs log record Michael Nishimoto
2008-04-08 15:50 ` David Chinner [this message]
2008-04-08 16:14 ` Michael Nishimoto
2008-04-08 21:36 ` Michael Nishimoto
2008-04-09 2:30 ` David Chinner
2008-04-09 4:38 ` Timothy Shimmin
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=20080408155043.GZ108924158@sgi.com \
--to=dgc@sgi.com \
--cc=miken@agami.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox