From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Lawrence Ong <lawrence.ong@netregistry.com.au>,
nfs@lists.sourceforge.net
Subject: Re: SM_UNMON again -> kernel
Date: 14 Jul 2003 10:56:01 +0200 [thread overview]
Message-ID: <shsptkdij1a.fsf@charged.uio.no> (raw)
In-Reply-To: <87k7aml330.fsf@ceramic.fifi.org>
>>>>> " " == Philippe Troin <phil@fifi.org> writes:
> On machine #1: ceramic rpc.statd[30693]: Received erroneous
> SM_UNMON request from ceramic for 216.27.190.149
> On machine #2: tantale rpc.statd[18416]: Received erroneous
> SM_UNMON request from tantale for 216.27.190.148
OK. Hang on... The above looks more like stale entries due to somebody
having permanently switched off a server on which ceramic/tantale were
holding locks.
Could you check on 'ceramic', and 'tantale' if they don't have entries
for 216.27.190.149 and 216.27.190.148 respectively in /var/lib/nfs/sm
or /var/lib/nfs/sm.bak?
Another mistake that can cause the above errors is if the sysman has
made those 2 directories NFS shared between different clients. (Not a
good idea...)
Cheers,
Trond
-------------------------------------------------------
This SF.Net email sponsored by: Parasoft
Error proof Web apps, automate testing & more.
Download & eval WebKing and get a free book.
www.parasoft.com/bulletproofapps1
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-07-14 8:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-11 6:16 SM_UNMON again -> kernel Lawrence Ong
2003-07-11 9:38 ` Trond Myklebust
2003-07-13 3:22 ` Philippe Troin
2003-07-13 15:25 ` Trond Myklebust
2003-07-13 18:00 ` Philippe Troin
2003-07-13 23:36 ` Lawrence Ong
2003-07-14 8:56 ` Trond Myklebust [this message]
2003-07-18 1:08 ` Philippe Troin
2003-07-19 3:26 ` Philippe Troin
2003-07-19 16:22 ` Christian Reis
2003-07-20 23:28 ` Trond Myklebust
2003-07-20 23:45 ` Christian Reis
2003-07-21 13:08 ` Bogdan Costescu
2003-07-13 4:25 ` Lawrence Ong
2003-07-14 8:47 ` Trond Myklebust
2003-07-14 23:42 ` Lawrence Ong
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=shsptkdij1a.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=lawrence.ong@netregistry.com.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 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.