From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: "Albers, Lucas" <luke@coe.montana.edu>
Cc: "'nfs@lists.sourceforge.net'" <nfs@lists.sourceforge.net>,
"'Valhalla-list@redhat.com'" <Valhalla-list@redhat.com>
Subject: Re: Error mounting nfs clients
Date: 27 Nov 2002 21:46:37 +0100 [thread overview]
Message-ID: <shsbs4aeo5u.fsf@charged.uio.no> (raw)
In-Reply-To: <E2A41F3CFE5FD411ABC900508BAE0BEE02CAF4F2@power.coe.montana.edu>
>>>>> " " == Lucas Albers <Albers> writes:
> After researching the issue. It appears that the error is
> related to the defined value:
> NFS_FHSIZE
> in the code listed below in this file:
> /usr/src/linux-2.4.18-5/fs/nfsd/nfsctl.c
> /*-----------------------------------------------------*/
> if (err == 0) {
> if (fh.fh_size > NFS_FHSIZE)
> err = -EINVAL;
> /*-----------------------------------------------------*/
> It appears that raising the value:
> #define NFS_FHSIZE 32
> Defined in /usr/include/linux/nfs.h Would fix the problem.
If you do that, you will no longer be running NFSv2. Under NFSv2, file
handle sizes are 32 bytes long, no more, no less...
If the filesystem you are using needs to generate filehandles that are
greater that 32 bytes long, then you will probably only be able to use
it with NFSv3
Cheers,
Trond
-------------------------------------------------------
This SF.net email is sponsored by: Get the new Palm Tungsten T
handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2002-11-27 20:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-27 18:50 Error mounting nfs clients Albers, Lucas
2002-11-27 20:46 ` Trond Myklebust [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=shsbs4aeo5u.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=Valhalla-list@redhat.com \
--cc=luke@coe.montana.edu \
--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 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.