Re: autofs config
Reco <recoverym4n@gmail.com> writes:
[...]
> Won't it be fun otherwise?
>
> The good thing is - autofs is working as intended.
> The bad thing is - mount is failing.
,----
| NOTE: I've rearranged your post to put the next question and answer at
| the bottom of this reply
`----
[...] missing q and a
>> One question... am I supposed to create the directories
>> /projects/dv /projects/d0 ?
>>
>> It appears from the instructions I've seen that .. no I am not to
>> create those dir... just /projects/. however, I did try it both ways
>> and can report that nothing gets mounted in either test.
>
> No, you definitely do not. Either autofs creates a directory for you, or
> you're unable to mount it. Top-level directory *must* be created, but
> you did it.
Well at least I got that part right.
[...]
>> /projects /etc/auto.net --timeout=180 (Note: It now says `auto.net')
>> +dir:/etc/auto.master.d
>> +auto.master
>
Reco wrote
> Should be something like this:
>
> /projects program:/etc/auto.net --timeout=180
Ok, commented out the 2 lines that were uncommented by default
[...]
> A small nit. Do not use 'hard' mount option unless you absolutely need
> it. It is painful, and it's by design. It has nothing to do with your
> current problem, though. What you probably need is:
>
> -fstype=nfs4,soft,intr,nodev,nosuid,async
All right, good to know.
------- ------- ---=--- ------- -------
And now the question answer I moved:
Reco Wrote:
> Which brings me to this:
>
> 1) What security option are you using (i.e. none, sys, krb5, etc)?
> If unsure, please mount a share by hand and obtain mount options
> from /proc/mounts.
It appears to be sys (sec=sys)
192.168.1.42:/projects/dv /projects/dv nfs4 rw,relatime,vers=4.0,\
rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,port=0,\
timeo=600,retrans=2,sec=sys,clientaddr=192.168.1.29,local_lock=none,\
^^^^^^^
addr=192.168.1.42 0 0
[...]
> 3) Stop autofs, start it like this:
>
> /usr/sbin/automount -fd
>
> Mount a filesystem. Watch the debug output. Terminate it with Ctrl+C.
(below I marked with *** what might be a clue)
------- ------- ---=--- ------- -------
parse_init: parse(sun): init gathered global options: (null)
spawn_mount: mtab link detected, passing -n to mount
spawn_umount: mtab link detected, passing -n to mount
mounted indirect on /test with timeout 90, freq 23 seconds
st_ready: st_ready(): state = 0 path /test
handle_packet: type = 3
handle_packet_missing_indirect: token 47, name dv, request pid 11696
attempting to mount entry /test/dv
lookup_mount: lookup(file): looking up dv
lookup_mount: lookup(file): dv -> --fstype=nfs4,rw,soft,intr 191.168.1.42:/test
parse_mount: parse(sun): expanded entry: --fstype=nfs4,rw,soft,intr 191.168.1.42:/test
parse_mount: parse(sun): gathered options: -fstype=nfs4,rw,soft,intr
parse_mount: parse(sun): dequote("191.168.1.42:/test") -> 191.168.1.42:/test
parse_mount: parse(sun): core of entry: options=-fstype=nfs4,rw,soft,intr, loc=191.168.1.42:/test
sun_mount: parse(sun): mounting root /test, mountpoint dv, what 191.168.1.42:/test, fstype nfs, options -fstype=nfs4,rw,soft,intr
mount_mount: mount(nfs): root=/test name=dv what=191.168.1.42:/test, fstype=nfs, options=-fstype=nfs4,rw,soft,intr
mount_mount: mount(nfs): nfs options="-fstype=nfs4,rw,soft,intr", nobind=0, nosymlink=0, ro=0
get_nfs_info: called with host 191.168.1.42(191.168.1.42) proto 6 version 0x30
get_nfs_info: called with host 191.168.1.42(191.168.1.42) proto 17 version 0x30
*** mount(nfs): no hosts available
dev_ioctl_send_fail: token = 47
failed to mount /test/dv
handle_packet: type = 3
handle_packet_missing_indirect: token 48, name dv, request pid 11696
dev_ioctl_send_fail: token = 48
st_expire: state 1 path /test
expire_proc: exp_proc = 140662262839040 path /test
expire_cleanup: got thid 140662262839040 path /test stat 0
expire_cleanup: sigchld: exp 140662262839040 finished, switching from 2 to 1
st_ready: st_ready(): state = 2 path /test
st_expire: state 1 path /test
expire_proc: exp_proc = 140662262839040 path /test
expire_cleanup: got thid 140662262839040 path /test stat 0
expire_cleanup: sigchld: exp 140662262839040 finished, switching from 2 to 1
st_ready: st_ready(): state = 2 path /test
[...]
------- ------- ---=--- ------- -------
As I mentioned in the OP:
The host involved is a solaris x86 host. The file systems set for
nfs availability are not put into an /etc/exports type setup.
The way it is done on solaris with the zfs file system... is during
the creation of a file system with `zfs create'
One usees an option (-o) that looks like:
zfs create -o sharenfs=on -o sharesmb=on somezpool/some/path
So in the case above nfs (and smb access) will be turned on.
So maybe that has something to do with the problem...
But then again, maybe not. Because as I have demonstrated, the share
is readily recognized by this Debian host in a manual nfs mount.
Reply to: