xfs
[Top] [All Lists]

Re: bad log entries after remount with XFS over MD in 2.6

To: Andi Kleen <ak@xxxxxxxxxxxxx>
Subject: Re: bad log entries after remount with XFS over MD in 2.6
From: Nathan Scott <nathans@xxxxxxx>
Date: Fri, 22 Aug 2003 21:31:42 +1000
Cc: linux-xfs@xxxxxxxxxxx
In-reply-to: <20030822093043.GA79023@xxxxxxxxxxxxx>; from ak@xxxxxxxxxxxxx on Fri, Aug 22, 2003 at 11:30:43AM +0200
References: <20030821194432.GA12755@averell> <20030822002801.GB823@frodo> <20030822093043.GA79023@xxxxxxxxxxxxx>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/1.2.5i
On Fri, Aug 22, 2003 at 11:30:43AM +0200, Andi Kleen wrote:
> > 
> > Recovery doesn't really look inside the payload of each log record
> > until it has a good idea of exactly where the log head and tail are.
> > 
> > Other than this I have no hints.  I don't see this behaviour on
> > non-MD devices just as a data point.  From your logprint it looks
> 
> Yes, non-MD works fine for me too.
> 
> > like the log writes are the problem (as opposed to the log reads
> > that recovery does).  We do funky stuff there - write different
> > size chunks at arbitrary 512 byte offsets... has caused problems
> > for busted drivers in the past, maybe something along those lines
> > again.
> 
> Possible yes. MD hasn't been exactly trouble free in 2.5 so far with
> the new BIO code.
> 
> The log is never cleared on recovery right?

Thats correct.  At the end of recovery the log head and tail
both point at the same block and all new log writes proceed
from wherever that happens to be in the log.

cheers.

-- 
Nathan


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