From: dek_ml@konerding.com
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: neilb@cse.unsw.edu.au (Neil Brown),
linux-kernel@vger.kernel.org, nfs@lists.sourceforge.net,
mason@suse.com, dek_ml@konerding.com
Subject: Re: problems with reiserfs + nfs using 2.4.2-pre4
Date: Mon, 19 Feb 2001 18:11:23 -0800 [thread overview]
Message-ID: <200102200211.f1K2BO002802@konerding.com> (raw)
In-Reply-To: Your message of "Tue, 20 Feb 2001 01:24:27 GMT." <E14V1Xa-0005Bf-00@the-village.bc.nu>
Alan Cox writes:
>> This may seem like a lot, but several of these are already
>> requirements which most filesystems don't meet, and other are there
>> to tidy-up interfaces and make locking more straight forward.
>
>As a 2.5 thing it sounds like a very sensible path. It will also provide
>some of the operations groundwork needed for file systems that can only use
>NFS4 temporary handles
>
OK so I think what I can take from this is: for kernel 2.4 in the foreseeable
future, reiserfs over NFS won't work without a special patch. And, filesystems
other than ext2 in general might not support NFS. This all has to do with
internal design decisions, results of people coding against those decisions,
possibly abusing the decisions to acheive their own goals, etc, etc, all
of which lead to problems when the underlying design decisions changed and broke
code which depended on the old decisions.
For the foreseeable future I am going to stick with ext2 for my NFS-exported
directories. I think these problems need to be carefully stated in the Configure.help
for each filesystem which does not support NFS ... Configure.help is often the
most authoritative and up-to-date technical description of a particular kernel's
capabilities.
Dave
next prev parent reply other threads:[~2001-02-20 2:12 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 [this message]
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 ` [NFS] " Trond Myklebust
2001-02-20 14:02 ` 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=200102200211.f1K2BO002802@konerding.com \
--to=dek_ml@konerding.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mason@suse.com \
--cc=neilb@cse.unsw.edu.au \
--cc=nfs@lists.sourceforge.net \
/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