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

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

 



On Tue, 2022-01-18 at 17:00 +0800, Yixun Lan wrote:
> Hi Ian Kent:
> 
> thanks for your quick reply
> 
> On 16:44 Tue 18 Jan     , Ian Kent wrote:
> > On Tue, 2022-01-18 at 16:27 +0800, Yixun Lan wrote:
> > > Hi Ian Kent:
> > > 
> > > Fabian reported a bug about failing to mount /net with autofs-
> > > 5.1.8,
> > > but have no problem with previous 5.1.6
> > > 
> > > I'm not able to reproduce this error (need more info about the
> > > settings)
> > > So write to the mailinglist to see if you can shed some light on
> > > this..
> > > 
> > > 
> > > The most verbose error messages like this:
> > > 
> > > Jan 11 13:53:09 khnum automount[3614]: mount_autofs_offset:
> > > failed to
> > > mount offset trigger  at 
> > > Jan 11 13:56:24 khnum automount[3614]: set_tsd_user_vars: failed
> > > to
> > > get
> > > buffer size for getpwuid_r
> > > Jan 11 14:56:52 khnum kernel:
> > > autofs4:pid:10191:validate_dev_ioctl:
> > > invalid path supplied for cmd(0xc018937e)
> > 
> > I've had several bug reports which have been mostly fixed now but
> > these
> > log entries don't look like anything I have seen so far.
> > 
> > I haven't yet pushed those changes to the repository either.
> > How would you like to proceed?
> > I could post a patch series to you or the list to try if you wish.
> either way work for me, but I need to be able to reproduce this first
> I will leave Fabian for comments..

A debug log is almost always what I ask for.

Setting "logging = debug" in /etc/autofs.conf will do it.
You need to get a log from start of automount to after the problem
occurs.


Ian




[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