From: Bjoern Voigt via GNU coreutils Bug Reports <bug-coreutils@gnu.org>
To: 68283@debbugs.gnu.org
Subject: bug#68283: ls -l issues on cifs mounted directories
Date: Sat, 6 Jan 2024 14:08:04 +0100 [thread overview]
Message-ID: <0857af15-c169-4cb0-a4a8-0488fec2e94f@arcor.de> (raw)
After upgrading coreutils from version 9.3 to 9.4, "ls -l" shows error
messages, if the files or directories are in a cifs/smb3 mounted directory.
Example:
/mnt/cifstest here is mounted with "mount -t cifs -o username=myuser
//192.168.1.2/all /mnt/cifstest/". The server is a Samba 4.19.2 server.
The kernel is version 6.1.71.
# ls -l /mnt/cifstest/
ls: /mnt/cifstest/: Resource temporarily unavailable
ls: /mnt/cifstest/opt: Resource temporarily unavailable
ls: /mnt/cifstest/dev: Resource temporarily unavailable
ls: /mnt/cifstest/var: Resource temporarily unavailable
ls: /mnt/cifstest/usr: Resource temporarily unavailable
ls: /mnt/cifstest/sbin: Resource temporarily unavailable
ls: /mnt/cifstest/boot: Resource temporarily unavailable
ls: /mnt/cifstest/lib: Resource temporarily unavailable
ls: /mnt/cifstest/etc: Resource temporarily unavailable
ls: /mnt/cifstest/lib64: Resource temporarily unavailable
ls: /mnt/cifstest/run: Resource temporarily unavailable
ls: /mnt/cifstest/proc: Resource temporarily unavailable
ls: /mnt/cifstest/lost+found: Resource temporarily unavailable
ls: /mnt/cifstest/root: Resource temporarily unavailable
ls: /mnt/cifstest/sys: Resource temporarily unavailable
ls: /mnt/cifstest/bin: Resource temporarily unavailable
ls: /mnt/cifstest/srv: Resource temporarily unavailable
ls: /mnt/cifstest/home: Resource temporarily unavailable
ls: /mnt/cifstest/mnt: Resource temporarily unavailable
ls: /mnt/cifstest/tmp: Resource temporarily unavailable
total 0
drwxr-xr-x 2 root root 0 Jan 6 12:01 bin
drwxr-xr-x 2 root root 0 Jan 5 20:47 boot
drwxr-xr-x 2 root root 0 Jan 6 13:14 dev
drwxr-xr-x 2 root root 0 Jan 5 21:00 etc
drwxr-xr-x 2 root root 0 Dec 6 22:54 home
drwxr-xr-x 2 root root 0 Jan 4 21:51 lib
drwxr-xr-x 2 root root 0 Jan 5 21:00 lib64
drwxr-xr-x 2 root root 0 Dec 21 2014 lost+found
drwxr-xr-x 2 root root 0 Jun 9 2021 mnt
drwxr-xr-x 2 root root 0 Dec 26 22:34 opt
drwxr-xr-x 2 root root 0 Jan 5 23:17 proc
drwxr-xr-x 2 root root 0 Dec 10 19:49 root
drwxr-xr-x 2 root root 0 Jan 6 13:53 run
drwxr-xr-x 2 root root 0 Jan 5 20:59 sbin
drwxr-xr-x 2 root root 0 Dec 27 2021 srv
drwxr-xr-x 2 root root 0 Jan 6 01:19 sys
drwxr-xr-x 2 root root 0 Jan 6 13:53 tmp
drwxr-xr-x 2 root root 0 Dec 10 19:49 usr
drwxr-xr-x 2 root root 0 Dec 12 08:37 var
"ls -l" from coreutils 9.3 does not show any errors.
Probably it is not just the error message. "dmesg -w" shows several
errors after executing "ls -l":
[17563.999109] smb2_reconnect: 3 callbacks suppressed
[17563.999113] CIFS: VFS: reconnect tcon failed rc = -11
[17564.160117] CIFS: VFS: reconnect tcon failed rc = -11
[17564.192244] CIFS: VFS: reconnect tcon failed rc = -11
[17564.223303] CIFS: VFS: reconnect tcon failed rc = -11
[17564.256080] CIFS: VFS: reconnect tcon failed rc = -11
[17564.287887] CIFS: VFS: reconnect tcon failed rc = -11
[17564.410323] CIFS: VFS: reconnect tcon failed rc = -11
[17564.442095] CIFS: VFS: reconnect tcon failed rc = -11
[17564.474065] CIFS: VFS: reconnect tcon failed rc = -11
[17564.569435] CIFS: VFS: reconnect tcon failed rc = -11
I debugged this problem a bit. The changes in
coreutils-9.4/lib/file-has-acl.c:file_has_acl are probably responsible
for the errors. The system call listxttr produces the error message
"Resource temporarily unavailable". I could not find the reasons for
error messages shown with "dmesg".
The listxattr.c test program in the manual page (man listxattr) shows
the following output:
# ./listxattr /mnt/cifstest/
listxattr: Resource temporarily unavailable
Work-around are to downgrade to coreutils 9.3 or not to use the "-l"
option for ls.
Björn
next reply other threads:[~2024-01-06 13:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-06 13:08 Bjoern Voigt via GNU coreutils Bug Reports [this message]
2024-01-06 14:48 ` bug#68283: ls -l issues on cifs mounted directories Pádraig Brady
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
List information: https://lists.gnu.org/mailman/listinfo/bug-coreutils
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0857af15-c169-4cb0-a4a8-0488fec2e94f@arcor.de \
--to=bug-coreutils@gnu.org \
--cc=68283@debbugs.gnu.org \
--cc=bjoernv@arcor.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).