From: Timothy Shimmin <tes@sgi.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: Lachlan McIlroy <lachlan@sgi.com>,
Eric Sandeen <sandeen@sandeen.net>,
xfs@oss.sgi.com
Subject: Re: [GIT PULL] XFS update for 2.6.23 - revert a commit
Date: Wed, 03 Oct 2007 11:49:11 +1000 [thread overview]
Message-ID: <4702F517.3040502@sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0710020442540.24427@p34.internal.lan>
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
next prev parent reply other threads:[~2007-10-03 1:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-01 7:23 [GIT PULL] XFS update for 2.6.23 - revert a commit Tim Shimmin
2007-10-01 12:55 ` Eric Sandeen
2007-10-01 13:05 ` Eric Sandeen
2007-10-01 13:12 ` Eric Sandeen
2007-10-02 1:41 ` Timothy Shimmin
2007-10-02 7:03 ` Lachlan McIlroy
2007-10-02 8:43 ` Justin Piszcz
2007-10-03 1:49 ` Timothy Shimmin [this message]
2007-10-03 8:11 ` Justin Piszcz
2007-10-04 0:26 ` David Chinner
2007-10-04 10:59 ` Justin Piszcz
2007-10-02 9:36 ` David Chinner
2007-10-01 15:02 ` Linus Torvalds
2007-10-02 0:13 ` 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=4702F517.3040502@sgi.com \
--to=tes@sgi.com \
--cc=jpiszcz@lucidpixels.com \
--cc=lachlan@sgi.com \
--cc=sandeen@sandeen.net \
--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