From: Chip Salzenberg <chip@pobox.com>
To: Tobias Diedrich <ranma@tdiedrich.de>
Cc: nfs@lists.sf.net
Subject: Re: NFSv3, 2.6, ext3 and dir_index
Date: Mon, 14 Mar 2005 12:22:34 -0500 [thread overview]
Message-ID: <20050314172234.GA11469@perlsupport.com> (raw)
In-Reply-To: <20050120163806.GA25242@melchior.yamamaya.is-a-geek.org>
According to Tobias Diedrich:
> Are there any known problems with dir_index and NFS, or is this
> maybe a new bug?
Did you ever get any replies on dir_index vs. nfs?
I'm just setting up a new server and I'm wondering if there's
something still out there that might make me sorry to use dir_index.
--
Chip Salzenberg - a.k.a. - <chip@pobox.com>
Open Source is not an excuse to write fun code
then leave the actual work to others.
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2005-03-14 17:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-23 20:55 More Stale NFS handles Eiwe Lingefors
2005-06-24 5:48 ` Frank Steiner
2005-06-24 6:15 ` Trond Myklebust
2005-06-24 6:47 ` Frank Steiner
2005-06-29 20:28 ` Kris Vassallo
2005-01-20 16:38 ` NFSv3, 2.6, ext3 and dir_index Tobias Diedrich
2005-03-14 17:22 ` Chip Salzenberg [this message]
2005-03-20 21:21 ` Tobias Diedrich
2005-08-13 9:39 ` Tobias Diedrich
2005-06-29 20:50 ` More Stale NFS handles Bill Rugolsky Jr.
2005-06-29 21:04 ` Trond Myklebust
-- strict thread matches above, loose matches on Subject: below --
2005-01-20 16:38 NFSv3, 2.6, ext3 and dir_index Tobias Diedrich
2005-01-20 19:26 ` Michael Haverkamp
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=20050314172234.GA11469@perlsupport.com \
--to=chip@pobox.com \
--cc=nfs@lists.sf.net \
--cc=ranma@tdiedrich.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.