From: Timothy Shimmin <tes@sgi.com>
To: "Jonathan C. Detert" <Jonathan.Detert@msoe.edu>
Cc: xfs@oss.sgi.com
Subject: Re: mount prob: "log inconsistent or not a log"
Date: Thu, 20 Dec 2007 16:45:33 +1100 [thread overview]
Message-ID: <476A017D.2020106@sgi.com> (raw)
In-Reply-To: <20071220050445.GA3212@msoe.edu>
Jonathan C. Detert wrote:
>
>> If there's corruption that was not between the tail to the head,
>> then it could be a goer I guess but one would wonder about corruption
>
> what do you mean by 'goer' - hardware failure?
>
I was just thinking that if there was corruption just confined to the
log but not in the interval between the tail and head then
I can't see why theoretically the log can't be replayed.
The replay of the log is done from the tail to the head - the
other log data is mostly irrelevant in this case AFAICT
(I think the failure came with code which is trying to deal
with the case with a new filesystem where part of the log
is not written to yet so has zero cycle#s - but here we have
wrapped 598 times or whatever it was).
--Tim
next prev parent reply other threads:[~2007-12-20 5:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-20 0:01 mount prob: "log inconsistent or not a log" Jonathan.Detert
2007-12-20 0:53 ` Timothy Shimmin
2007-12-20 1:16 ` Jonathan C. Detert
2007-12-20 4:44 ` Timothy Shimmin
2007-12-20 5:04 ` Jonathan C. Detert
2007-12-20 5:45 ` Timothy Shimmin [this message]
2007-12-20 19:54 ` Jonathan C. Detert
2007-12-20 1:18 ` Jonathan C. Detert
2007-12-20 1:54 ` David Chinner
2007-12-20 2:44 ` Jonathan C. Detert
2007-12-20 17:55 ` Jonathan C. Detert
2007-12-21 0:47 ` Timothy Shimmin
2007-12-21 1:55 ` Jonathan C. Detert
2007-12-21 6:40 ` Timothy Shimmin
2007-12-21 23:19 ` Jonathan C. Detert
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=476A017D.2020106@sgi.com \
--to=tes@sgi.com \
--cc=Jonathan.Detert@msoe.edu \
--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