All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Reis <andreas.reis@gmail.com>
To: autofs@vger.kernel.org
Subject: NFSv4: Unable to mount, nonsensical error
Date: Sat, 27 Sep 2014 16:27:15 +0200	[thread overview]
Message-ID: <5426C943.1060307@gmail.com> (raw)

Hi,

I'm trying to automount a NFSv4 share to /mnt/bar from Host A via a 
direct map, but can't get it to work no matter what.

Mounting it manually with the very same options works perfectly fine.

auto.master:
/-     /etc/autofs/bar.nfs    --timeout=15 --ghost
/foo   /etc/autofs/auto.nfs   --timeout=15

The second line is an executable map for NFSv3 shares from Host B. That 
one works as intended. However…

fs.nfs:
/mnt/bar -fstype=nfs4,rw,soft,async,_netdev,rsize=8192,wsize=8192 
192.168.1.144:bar
(on one line)

… fails. Instead, the folder is still created, but accessing it yields 
"No such file or directory".

Meanwhile automount prints a nonsensical …

"validate_location: expected colon delimeter not found in location 
192.168.1.144:bar"

… which from an error path (with a typo) in parse_sun.c's 
validate_location that was added in autofs 5.0.6.

Maybe the person who added it missed that unlike mount requests for 
NFSv3 shares, NFSv4 ones need not (depending on the server, must not) 
have a "/" after the ":"?

Because that however is what the somewhat misleadingly named check_colon 
function called by validate_location checks.

Nonetheless, patching that path to still return 1 resolved nothing.

Any ideas?

(Distro is Arch, updated packages, ie. autofs 5.1.0.)

Thanks,
Andreas

             reply	other threads:[~2014-09-27 14:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-27 14:27 Andreas Reis [this message]
2014-09-28  2:10 ` NFSv4: Unable to mount, nonsensical error Ian Kent

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=5426C943.1060307@gmail.com \
    --to=andreas.reis@gmail.com \
    --cc=autofs@vger.kernel.org \
    /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.