sloppy mount and lockd
Hi Ian,
I get these in the kernel log
svc: failed to register lockdv1 RPC service error no. 97
I have no idea why but using fstab does not produce these errors so just curious if they are troublesome or if you have seen this before. I have had autofs die a couple of times and wondering if its related to this in any way.
Also if you have an idea why the mounts show as "sloppy" for my Autofs mounts but not fstab mounts?. I read that it is to support unrecognized options from the NFS servers such as -nobrowse. Is there a way to prevent this or can it be safely ignored?
Thank you
J
Ian Kent
maintainerQuoted 8 lines · Techie
Hi Ian,
I get these in the kernel log
svc: failed to register lockdv1 RPC service error no. 97
I have no idea why but using fstab does not produce these errors so just curious if they are troublesome or if you have seen this before. I have had autofs die a couple of times and wondering if its related to this in any way.
Haven't heard of this before.
Don't know enough about the problem so can't say if it is related.
Quoted 5 lines
Also if you have an idea why the mounts show as "sloppy" for my Autofs mounts but not fstab mounts?. I read that it is to support unrecognized options from the NFS servers such as -nobrowse. Is there a way to prevent this or can it be safely ignored?
Not quite.
autofs pseudo options like nobrowse usually don't to actual nfs mounts. In the past there have been commonly used mount options that were not supported by Linux mount and the sloppy option is used to tell mount to ignore invalid options rather than fail. You should be able to ignore this.
Ian