From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Roman Zippel <zippel@fh-brandenburg.de>
Cc: Neil Brown <neilb@cse.unsw.edu.au>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
dek_ml@konerding.com, linux-kernel@vger.kernel.org,
nfs@lists.sourceforge.net, mason@suse.com
Subject: Re: [NFS] Re: problems with reiserfs + nfs using 2.4.2-pre4
Date: 20 Feb 2001 10:44:07 +0100 [thread overview]
Message-ID: <shslmr11yfs.fsf@charged.uio.no> (raw)
In-Reply-To: <Pine.GSO.4.10.10102200330330.25095-100000@zeus.fh-brandenburg.de>
In-Reply-To: Roman Zippel's message of "Tue, 20 Feb 2001 03:38:32 +0100 (MET)"
>>>>> " " == Roman Zippel <zippel@fh-brandenburg.de> writes:
> Hi, On Tue, 20 Feb 2001, Neil Brown wrote:
>> 2/ lookup("..").
> A small question: Why exactly is this needed?
Short answer: the existence of 'rename' makes it necessary, since it
means that the directory path is volatile as far as the client is
concerned.
IIRC several NFS implementations (not Linux though) rely on being able
to walk back up the directory tree in order to discover the path at
any given moment.
Under Linux, our reliance on dentries doesn't allow for directory
paths to be volatile, so we don't support it. Instead we end up having
to support aliased directories.
Cheers,
Trond
next prev parent reply other threads:[~2001-02-20 9:44 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-19 0:18 problems with reiserfs + nfs using 2.4.2-pre4 dek_ml
2001-02-19 0:37 ` Neil Brown
2001-02-19 2:56 ` dek_ml
2001-02-19 3:40 ` Neil Brown
2001-02-19 11:23 ` Alan Cox
2001-02-20 0:40 ` Neil Brown
2001-02-20 1:15 ` Chris Mason
2001-02-20 1:34 ` Neil Brown
2001-02-20 1:24 ` Alan Cox
2001-02-20 1:37 ` Neil Brown
2001-02-20 2:11 ` dek_ml
2001-02-20 22:54 ` Brian May
2001-02-20 23:30 ` Chris Mason
2001-02-20 2:38 ` Roman Zippel
2001-02-20 9:44 ` Trond Myklebust [this message]
2001-02-20 14:02 ` [NFS] " Roman Zippel
2001-02-20 15:16 ` Trond Myklebust
2001-02-20 16:26 ` Roman Zippel
2001-02-21 3:02 ` Neil Brown
2001-02-21 12:43 ` [NFS] " Trond Myklebust
2001-02-19 1:55 ` Alan Cox
2001-02-19 15:37 ` Chris Mason
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=shslmr11yfs.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dek_ml@konerding.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mason@suse.com \
--cc=neilb@cse.unsw.edu.au \
--cc=nfs@lists.sourceforge.net \
--cc=zippel@fh-brandenburg.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox