From: "Jose R. Santos" <jrsantos@austin.ibm.com>
To: Garrick Staples <garrick@usc.edu>
Cc: nfs@lists.sourceforge.net
Subject: Re: mountd segfault on itanium2
Date: Mon, 3 May 2004 08:35:46 -0500 [thread overview]
Message-ID: <20040503133546.GA25469@rx8.ibm.com> (raw)
In-Reply-To: <20040501030730.GE23287@polop.usc.edu> (from garrick@usc.edu on Fri, Apr 30, 2004 at 22:07:30 -0500)
On 04/30/04 22:07:30, Garrick Staples wrote:
> I have an ugly work-around that seems to be working. It seems that 2.6 has a
> new nfs interface for userspace. By forcing mountd to use the older 2.4
> interface, it doesn't segfault anymore. So something in the new code paths is
> broken.
>
> In support/nfs/cachio.c:
> int
> check_new_cache(void)
> {
> struct stat stb;
>
> return 0; /* DISABLE NEW 2.6 INTERFACE */
>
> return (stat("/proc/fs/nfs/filehandle", &stb) == 0) ||
> (stat("/proc/fs/nfsd/filehandle", &stb) == 0);
> }
If you want to use the old syscall interface, all you need to do is make
sure nfsd is not mounted in /proc/fs/nfsd.
> Am I losing any functionality by doing this? I can't actually find any
> problems.
I think there are no functionality losses but I have seen issues with using
the syscall interface on large memory systems. The syscall mount and
unmount the nfsdfs for every syscall. This will cause the inode and dentry
for this filesystem to be flush, but in order to do that it needs to walk
through all inode and dentry caches under lock. If you have a system with
16GB of ram, mounting and unmounting can take a really long time.
-JRS
-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g.
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2004-05-03 13:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-30 21:24 mountd segfault on itanium2 Garrick Staples
2004-04-30 23:43 ` Garrick Staples
2004-05-01 0:15 ` J. Bruce Fields
2004-05-01 0:24 ` Garrick Staples
2004-05-01 3:07 ` Garrick Staples
2004-05-03 13:35 ` Jose R. Santos [this message]
2004-05-03 18:18 ` Garrick Staples
2004-05-03 18:24 ` Garrick Staples
2004-05-03 20:47 ` Garrick Staples
2004-05-04 0:17 ` Garrick Staples
2004-05-04 1:01 ` J. Bruce Fields
2004-05-04 1:52 ` Garrick Staples
2004-05-04 1:38 ` Garrick Staples
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=20040503133546.GA25469@rx8.ibm.com \
--to=jrsantos@austin.ibm.com \
--cc=garrick@usc.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.