Re: 5.1.8 s390x error: invalid path supplied for cmd(0xc018937e)

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

 



On Tue, 2022-01-04 at 09:57 -0300, Andreas Hasenack wrote:
> Hi,
> 
> the autopkgtests for autofs started to fail in Ubuntu in the s390x
> architecture only. The scenario is an authenticated localhost cifs
> mount.
> 
> When I try it, I get:
> root@j-s390x:~# l /cifs/localhost
> ls: cannot access '/cifs/localhost': No such file or directory
> 
> I get this in syslog:
> Jan  4 12:52:48 j-s390x automount[1969]: mount_autofs_offset: failed
> to mount offset trigger  at
> Jan  4 12:52:48 j-s390x automount[1969]: message repeated 2 times: [
> mount_autofs_offset: failed to mount offset trigger  at ]
> Jan  4 12:52:48 j-s390x automount[1969]: mount_subtree: parse(sun):
> failed to mount offset triggers
> Jan  4 12:52:48 j-s390x kernel: [ 1582.465030]
> autofs4:pid:1991:validate_dev_ioctl: invalid path supplied for
> cmd(0xc018937e)
> Jan  4 12:52:48 j-s390x kernel: [ 1582.465306]
> autofs4:pid:1991:validate_dev_ioctl: invalid path supplied for
> cmd(0xc018937e)
> Jan  4 12:52:48 j-s390x kernel: [ 1582.465358]
> autofs4:pid:1991:validate_dev_ioctl: invalid path supplied for
> cmd(0xc018937e)
> Jan  4 12:52:48 j-s390x kernel: [ 1582.465405]
> autofs4:pid:1991:validate_dev_ioctl: invalid path supplied for
> cmd(0xc018937e)
> Jan  4 12:52:48 j-s390x kernel: [ 1582.465409]
> autofs4:pid:1991:validate_dev_ioctl: invalid path supplied for
> cmd(0xc018937e)
> Jan  4 12:52:48 j-s390x kernel: [ 1582.465412]
> autofs4:pid:1991:validate_dev_ioctl: invalid path supplied for
> cmd(0xc018937e)
> 
> With 5.1.7, it works:
> root@j-s390x:~# l /cifs
> total 4.0K
> drwxr-xr-x  2 root root    0 Jan  4 12:55 .
> drwxr-xr-x 23 root root 4.0K Jan  4 12:55 ..
> root@j-s390x:~# l /cifs/localhost
> total 0
> drwxr-xr-x 5 root root 0 Jan  4 12:55  .
> drwxr-xr-x 3 root root 0 Jan  4 12:55  ..
> drwxr-xr-x 2 root root 0 Dec 27 20:14 'print$'
> drwxr-xr-x 2 root root 0 Dec 27 20:15  private
> drwxr-xr-x 2 root root 0 Dec 27 20:15  pub
> root@j-s390x:~# l /cifs/localhost/private
> total 4.0K
> drwxr-xr-x 2 root root  0 Dec 27 20:15 .
> drwxr-xr-x 5 root root  0 Jan  4 12:55 ..
> -rwxr-xr-x 1 root root 64 Dec 29 17:16 hello-private.txt
> 
> and syslog shows just:
> Jan  4 12:55:54 j-s390x kernel: [ 1768.290258] CIFS: Attempting to
> mount \\localhost\pub
> Jan  4 12:55:54 j-s390x kernel: [ 1768.318174] CIFS: Attempting to
> mount \\localhost\private
> Jan  4 12:55:54 j-s390x kernel: [ 1768.328218] CIFS: Attempting to
> mount \\localhost\print$
> 
> 
> I have this config:
> root@j-s390x:~# cat /etc/auto.master|grep -vE "^($|#)"
> +dir:/etc/auto.master.d
> +auto.master
> /cifs /etc/auto.smb --timeout=180
> 
> The shares:
> [pub]
>   path = /pub
>   read only = no
>   guest ok = yes
> [private]
>   path = /private
>   read only = no
>   guest ok = no
> 
> root@j-s390x:~# cat /etc/creds/localhost
> username=smbtest9614
> password=9614
> domain=WORKGROUP
> 
> I see the 5.1.8 patches directory has a ton of patches, is this a
> known issue already perhaps? Or do you have any other troubleshooting
> tips?

Maybe, can I get a debug log please.

Set "logging = debug" (without the comment marker of course) then
use "journalctl | grep automount" to get the entries or if your
using syslog a similar grep should get the log entries.

I always ask for log output from starting up autofs until after
the problem has occurred.

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