xfs
[Top] [All Lists]

Re: mount prob: "log inconsistent or not a log"

To: "Jonathan C. Detert" <Jonathan.Detert@xxxxxxxx>
Subject: Re: mount prob: "log inconsistent or not a log"
From: Timothy Shimmin <tes@xxxxxxx>
Date: Thu, 20 Dec 2007 16:45:33 +1100
Cc: xfs@xxxxxxxxxxx
In-reply-to: <20071220050445.GA3212@msoe.edu>
References: <20071220000144.GQ19770@msoe.edu> <4769BD13.5040303@sgi.com> <20071220011601.GU19770@msoe.edu> <4769F343.9040405@sgi.com> <20071220050445.GA3212@msoe.edu>
Sender: xfs-bounce@xxxxxxxxxxx
User-agent: Thunderbird 2.0.0.9 (Macintosh/20071031)
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


<Prev in Thread] Current Thread [Next in Thread>