Re: autofs-5.1.8: fail to mount certain /net shares

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, 2022-01-26 at 11:22 +0100, Fabian Groffen wrote:
> On 26-01-2022 18:18:25 +0800, Yixun Lan wrote:
> > HI Fabian:
> > 
> > On 10:35 Wed 26 Jan     , Fabian Groffen wrote:
> > > On 21-01-2022 20:24:14 +0800, Ian Kent wrote:
> > > > > (this is identical to the 5.1.6 output)
> > > > > 
> > > > > build-log attached
> > > > 
> > > > That all looks good, including the build log.
> > > > 
> > > > How about we try stopping the autofs service and run automount
> > > > manually and see what we get.
> > > > 
> > > > Stop the service then run "automount -fd | tee autofs.log".
> > > > 
> > > > It might be useful to add a stderr redirect too but I usually
> > > > don't need it, eg. "automount -fd 2>&1 | tee autofs.log".
> > > 
> > > Sorry for the delay.
> > > 
> > > What I see is a difference in the mount sequence.
> > > 
> > > 5.1.6:
> > > 
> > > attempting to mount entry /net/host/export/gentoo
> > > lookup_mount: lookup(program): /net/host/export/gentoo -> -
> > > fstype=nfs4,hard,sec=sys,nodev,nosuid,wsize=32768,rsize=32768
> > > host:/export/gentoo
> > > parse_mount: parse(sun): expanded entry: -
> > > fstype=nfs4,hard,sec=sys,nodev,nosuid,wsize=32768,rsize=32768
> > > host:/export/gentoo
> > > parse_mount: parse(sun): gathered options:
> > > fstype=nfs4,hard,sec=sys,nodev,nosuid,wsize=32768,rsize=32768
> > > sun_mount: parse(sun): mounting root /net/host/export/gentoo,
> > > mountpoint /net/host/export/gentoo, what host:/export/gentoo,
> > > fstype nfs4, options
> > > hard,sec=sys,nodev,nosuid,wsize=32768,rsize=32768
> > > mount(nfs): root=/net/host/export/gentoo
> > > name=/net/host/export/gentoo what=host:/export/gentoo,
> > > fstype=nfs4,
> > > options=hard,sec=sys,nodev,nosuid,wsize=32768,rsize=32768
> > > mount(nfs): nfs
> > > options="hard,sec=sys,nodev,nosuid,wsize=32768,rsize=32768",
> > > nobind=0, nosymlink=0, ro=0
> > > get_nfs_info: called with host host(127.0.0.65) proto 6 version
> > > 0x40
> > > get_nfs_info: nfs v4 rpc ping time: 0.010256
> > > get_nfs_info: host host cost 10255 weight 0
> > > prune_host_list: selected subset of hosts that support NFS4 over
> > > TCP
> > > 
> > > while 5.1.8 does:
> > > 
> > > attempting to mount entry /net/host/export/gentoo
> > > lookup_mount: lookup(program): /net/host/export/gentoo -> -
> > > fstype=nfs,hard,nodev,nosuid host:/export/gentoo
> >                                                              
> > ~~~~~~~~~
> >                                         somehow, it pass the
> > "nfs(v3)" at begining?
> 
> yes, this is *identical* config, I just used a different binary.
> 
> If you look careful, you see that it also didn't take the rest of my
> options:
>   fstype=nfs4,hard,sec=sys,nodev,nosuid,wsize=32768,rsize=32768
> 
> So, either I'm not specifying them in a way supported by 5.1.8, or it
> somehow doesn't process them and falls back to some defaults.
> 
> Fabian
> 
> > 
> > > parse_mount: parse(sun): expanded entry: -
> > > fstype=nfs,hard,nodev,nosuid host:/export/gentoo
> > 
> > > parse_mount: parse(sun): gathered options:
> > > fstype=nfs,hard,nodev,nosuid
> > > sun_mount: parse(sun): mounting root /net/host/export/gentoo,
> > > mountpoint /net/host/export/gentoo, what host:/export/gentoo,
> > > fstype nfs, options hard,nodev,nosuid
> > > mount(nfs): root=/net/host/export/gentoo
> > > name=/net/host/export/gentoo what=host:/export/gentoo,
> > > fstype=nfs, options=hard,nodev,nosuid
> > > mount(nfs): nfs options="hard,nodev,nosuid", nobind=0,
> > > nosymlink=0, ro=0
> > > get_nfs_info: called with host host(127.0.0.65) proto 6 version
> > > 0x20
> > > get_nfs_info: nfs v3 rpc ping time: 0.008827
> > > get_nfs_info: host host cost 8827 weight 0
> > > get_nfs_info: called with host host(127.0.0.65) proto 17 version
> > > 0x20
> > > prune_host_list: selected subset of hosts that support NFS3 over
> > > TCP
> > > 
> > > So it's not using NFSv4 here.
> > > 
> > > Is this enough of the logs?  Else I need to do some more
> > > redaction here.

Can you please use "automount -fd 2>&1 | tee autofs.log" from the
command line, after stopping the serice of course, to get a debug
log for me.

It may be that I've missed a mail that has 5.1.8 logs, there's so
much of it these days ... but I don't have debug logs from the start
of automount until after problems occur.

Ian
> > > 
> > > Fabian
> > > 
> > > -- 
> > > Fabian Groffen
> > > Gentoo on a different level
> > 
> > 
> > 
> > -- 
> > Yixun Lan (dlan)
> > Gentoo Linux Developer
> > GPG Key ID AABEFD55
> 




[Index of Archives]     [Linux Filesystem Development]     [Linux Ext4]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux