From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Cajus Pollmeier <c.pollmeier@gmx.net>
Cc: nfs@lists.sourceforge.net
Subject: Re: NFS problems, UMON, missing directories, wrong permissions
Date: 06 May 2003 13:48:56 +0200 [thread overview]
Message-ID: <shsr87c70t3.fsf@charged.uio.no> (raw)
In-Reply-To: <200305061042.02405.c.pollmeier@gmx.net>
>>>>> " " == Cajus Pollmeier <c.pollmeier@gmx.net> writes:
> * Randomly missing directories / shredded permissions
> Either users don't see shared directories contents or have no
> permissions to access them. In fact they have, "id" shows up
> with the correct group membership and "ls -la" shows the
> directory group writable. After logging out and in again,
> everything's fine.
Please note that NFS doesn't support more than 16 groups. If the
permissions depend on the 17th group as listed by 'id', then it
probably won't work.
However that may not be the cause of your problem:
> May 6 07:12:59 terminalserver kernel: nsm:
> xdr_encode_mon(0a010002, -1249509120, 67108864, 268435456)
That's interesting. Looks like a pretty nasty stack corruption to
me. Are you running an Nvidia-tainted kernel by any chance?
Cheers,
Trond
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-05-06 11:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-06 8:41 NFS problems, UMON, missing directories, wrong permissions Cajus Pollmeier
2003-05-06 11:48 ` Trond Myklebust [this message]
2003-05-06 12:35 ` Trond Myklebust
2003-05-06 13:36 ` Cajus Pollmeier
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=shsr87c70t3.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=c.pollmeier@gmx.net \
--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.