From: Christof Koehler <christof.koehler@bccms.uni-bremen.de>
To: autofs@vger.kernel.org
Subject: Re: autofs reverts to IPv4 for multi-homed IPv6 server ?
Date: Fri, 8 Apr 2016 17:32:24 +0200 [thread overview]
Message-ID: <20160408153224.GY15153@bccms.uni-bremen.de> (raw)
In-Reply-To: <20160408142907.GX15153@bccms.uni-bremen.de>
Hello,
I might add that using an IPv6 address, i.e.
[2001:638:708:1261:2000::118]:/locals, in the automounter map does not
work either while an IPv4 address, i.e. 192.168.220.118:/locals, works
without a hitch. Is it desirable to be able to specify IPv6 addresses ?
I am just noting the inconsistency.
Have a nice weekend !
Apr 8 17:25:24 core324 automount[24310]: attempting to mount entry /local/core330
Apr 8 17:25:24 core324 automount[24310]: lookup_mount: lookup(program): core330 -> -fstype=nfs4,rw,intr,nosuid,soft,nodev 192.168.220.118:/locals
Apr 8 17:25:24 core324 automount[24310]: lookup_mount: lookup(program): looking up core330
Apr 8 17:25:24 core324 automount[24310]: lookup_mount: lookup(program): core330 -> -fstype=nfs4,rw,intr,nosuid,soft,nodev [2001:638:708:1261:2000::118]:/locals
Apr 8 17:25:24 core324 automount[24310]: parse_mount: parse(sun): expanded entry: -fstype=nfs4,rw,intr,nosuid,soft,nodev [2001:638:708:1261:2000::118]:/locals
Apr 8 17:25:24 core324 automount[24310]: parse_mount: parse(sun): gathered options: fstype=nfs4,rw,intr,nosuid,soft,nodev
Apr 8 17:25:24 core324 automount[24310]: parse_mount: parse(sun): dequote("[2001:638:708:1261:2000::118]:/locals") -> [2001:638:708:1261:2000::118]:/locals
Apr 8 17:25:24 core324 automount[24310]: parse_mount: parse(sun): core of entry: options=fstype=nfs4,rw,intr,nosuid,soft,nodev,loc=[2001:638:708:1261:2000::118]:/locals
Apr 8 17:25:24 core324 automount[24310]: sun_mount: parse(sun): mounting root /local, mountpoint core330, what [2001:638:708:1261:2000::118]:/locals, fstype nfs4, options rw,intr,nosuid,soft,nodev
Apr 8 17:25:24 core324 automount[24310]: mount_mount: mount(nfs): root=/local name=core33
0 what=[2001:638:708:1261:2000::118]:/locals, fstype=nfs4, options=rw,intr,nosuid,soft,nod
ev
Apr 8 17:25:24 core324 automount[24310]: mount_mount: mount(nfs): nfs options="rw,intr,no
suid,soft,nodev", nobind=0, nosymlink=0, ro=0
Apr 8 17:25:24 core324 automount[24310]: mount(nfs): no hosts available
Apr 8 17:25:24 core324 automount[24310]: dev_ioctl_send_fail: token = 1923
Apr 8 17:25:24 core324 automount[24310]: failed to mount /local/core330
Apr 8 17:25:24 core324 automount[24310]: handle_packet: type = 3
Apr 8 17:25:24 core324 automount[24310]: handle_packet_missing_indirect: token 1924, name core330, request pid 24519
Apr 8 17:25:24 core324 automount[24310]: dev_ioctl_send_fail: token = 1924
Best Regards
Christof
--
Dr. rer. nat. Christof Köhler email: c.koehler@bccms.uni-bremen.de
Universitaet Bremen/ BCCMS phone: +49-(0)421-218-62334
Am Fallturm 1/ TAB/ Raum 3.12 fax: +49-(0)421-218-62770
28359 Bremen
PGP: http://www.bccms.uni-bremen.de/cms/people/c_koehler/
--
To unsubscribe from this list: send the line "unsubscribe autofs" in
next prev parent reply other threads:[~2016-04-08 15:32 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-07 14:19 autofs reverts to IPv4 for multi-homed IPv6 server ? Christof Koehler
2016-04-08 4:46 ` Ian Kent
2016-04-08 10:10 ` Ian Kent
2016-04-08 10:14 ` Ian Kent
2016-04-08 12:25 ` Christof Koehler
2016-04-08 14:29 ` Christof Koehler
2016-04-08 15:32 ` Christof Koehler [this message]
2016-04-10 2:09 ` Ian Kent
2016-04-08 16:12 ` Christof Koehler
2016-04-08 16:15 ` Christof Koehler
2016-04-10 2:17 ` Ian Kent
2016-04-10 2:14 ` Ian Kent
2016-04-09 1:42 ` Ian Kent
2016-04-09 9:56 ` Christof Koehler
2016-04-10 2:29 ` Ian Kent
2016-04-25 4:40 ` Ian Kent
2016-04-25 15:06 ` Christof Koehler
2016-04-26 1:06 ` Ian Kent
2016-04-26 9:53 ` Ian Kent
2016-04-26 15:27 ` Christof Koehler
2016-04-27 1:54 ` Ian Kent
2016-04-27 2:27 ` Ian Kent
2016-04-27 16:52 ` Christof Koehler
2016-04-28 2:56 ` Ian Kent
2016-04-28 3:21 ` Ian Kent
2016-04-28 9:12 ` Christof Koehler
2016-04-28 9:10 ` Christof Koehler
2016-04-28 10:50 ` Ian Kent
2016-04-28 11:26 ` Christof Koehler
2016-04-28 12:40 ` Christof Koehler
2016-04-29 1:54 ` Ian Kent
2016-04-29 14:10 ` Christof Koehler
2016-04-29 14:42 ` Christof Koehler
2016-04-30 3:21 ` Ian Kent
2016-04-30 11:36 ` Christof Koehler
2016-04-30 15:15 ` Christof Koehler
2016-04-30 15:16 ` Christof Koehler
2016-05-02 6:01 ` Ian Kent
2016-05-02 16:08 ` Christof Koehler
2016-05-03 7:58 ` Ian Kent
2016-05-03 15:13 ` Christof Koehler
2016-05-04 7:20 ` Ian Kent
2016-05-04 12:38 ` Christof Koehler
2016-04-09 1:35 ` Ian Kent
2016-04-11 2:42 ` Ian Kent
2016-04-11 16:32 ` Christof Koehler
2016-04-11 16:35 ` Christof Koehler
2016-04-12 1:07 ` Ian Kent
2016-04-08 11:47 ` Christof Koehler
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=20160408153224.GY15153@bccms.uni-bremen.de \
--to=christof.koehler@bccms.uni-bremen.de \
--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.