From: Ian Kent <raven@themaw.net>
To: Techie <techchavez@gmail.com>
Cc: autofs@linux.kernel.org
Subject: Re: sloppy mount and lockd
Date: Wed, 17 Mar 2010 10:39:25 +0800 [thread overview]
Message-ID: <1268793565.2256.6.camel@localhost> (raw)
In-Reply-To: <dc3ecf561003161132v323efa21u8d7fc8a4e3d53f03@mail.gmail.com>
On Tue, 2010-03-16 at 11:32 -0700, Techie wrote:
> 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.
>
> 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
next prev parent reply other threads:[~2010-03-17 2:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-16 18:32 sloppy mount and lockd Techie
2010-03-17 2:39 ` Ian Kent [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-03-16 19:03 Techie
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=1268793565.2256.6.camel@localhost \
--to=raven@themaw.net \
--cc=autofs@linux.kernel.org \
--cc=techchavez@gmail.com \
/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.