xfs
[Top] [All Lists]

Re: [GIT PULL] XFS update for 2.6.23 - revert a commit

To: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
Subject: Re: [GIT PULL] XFS update for 2.6.23 - revert a commit
From: Timothy Shimmin <tes@xxxxxxx>
Date: Wed, 03 Oct 2007 11:49:11 +1000
Cc: Lachlan McIlroy <lachlan@xxxxxxx>, Eric Sandeen <sandeen@xxxxxxxxxxx>, xfs@xxxxxxxxxxx
In-reply-to: <Pine.LNX.4.64.0710020442540.24427@p34.internal.lan>
References: <20071001072350.DF61C58C4C0A@chook.melbourne.sgi.com> <4700EE2A.1020304@sandeen.net> <4701A1D0.5010709@sgi.com> <4701ED51.8050706@sgi.com> <Pine.LNX.4.64.0710020442540.24427@p34.internal.lan>
Sender: xfs-bounce@xxxxxxxxxxx
User-agent: Thunderbird 2.0.0.6 (Macintosh/20070728)
Hi Justin,

Justin Piszcz wrote:


On Tue, 2 Oct 2007, Lachlan McIlroy wrote:

Yeah that about sums it up. In an attempt to prevent log replay of inodes
in cases when we shouldn't replay we also prevented log replay of inodes in
cases when we should replay. We end up with directories that refer to inodes
that were not replayed and we read existing data off disk. That existing
data is usually previous instances of inodes. We had cases of regular files
turning into directories and inode version mismatches.


Lachlan

In 2.6.23-rc8?

The bad change went into rc7 and was still there in rc8.
It was backed out for rc9.

--Tim


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