From: "Theodore Ts'o" <tytso@mit.edu>
To: Frank van Maarseveen <frankvm@xs4all.nl>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [2.4.24-pre3] 0/5 EXT2/3 Updates
Date: Sat, 3 Jan 2004 19:44:51 -0500 [thread overview]
Message-ID: <20040104004451.GB2364@thunk.org> (raw)
In-Reply-To: <20040104000747.GA1706@janus>
On Sun, Jan 04, 2004 at 01:07:47AM +0100, Frank van Maarseveen wrote:
> On Thu, Jan 01, 2004 at 04:50:20PM -0500, Theodore Ts'o wrote:
> > Patch 5: Add HTREE indexed directory support
>
> Will this work on an NFS server? I remember an issue regarding a cookie
> representing the directory offset: The problem was that the conversion
> to HTREE of a directory while at the same time reading that directory
> over NFS would basically invalidate the directory offset.
Yes, it will work over an NFS server. We solve this problem by having
readdir() always return directory entries of small directories (which
are eligible to be converted into HTREE format) in hash order.
- Ted
prev parent reply other threads:[~2004-01-04 0:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-01 21:50 [PATCH] [2.4.24-pre3] 0/5 EXT2/3 Updates Theodore Ts'o
2004-01-04 0:07 ` Frank van Maarseveen
2004-01-04 0:44 ` Theodore Ts'o [this message]
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=20040104004451.GB2364@thunk.org \
--to=tytso@mit.edu \
--cc=frankvm@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
/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