Re: SM_UNMON again -> kernel

[Philippe Troin <phil@fifi.org>]

Philippe Troin <phil@fifi.org> writes:

> Trond Myklebust <trond.myklebust@fys.uio.no> writes:
> 
> > >>>>> " " == 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.
> 
> Nope, the machines have been rebooted...
>  
> > 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?
> 
> They have indeed very old files there that were removed.
> 
> > 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...)
> 
> No, that not the case. But I can see why it would wreak havoc.
> 
> Anyways, this is what I did:
> 
>  - I shut down all boxes interacting via NFS.
> 
>  - When booting them up, I switched to single-user mode and:
> 
>      * wiped /var/lib/nfs/mtab
> 
>      * removed any files in /var/lib/nfs/sm{,.bak}
> 
> And we'll see if the message shows up again.

And it did...

I still see the same messages over and over again.

Phil.


-------------------------------------------------------
This SF.net email is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single machine.
WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the
same time. Free trial click here: http://www.vmware.com/wl/offer/345/0
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs