search

clearlinux / distribution

Placeholder repository to allow filing of general bugs/issues/etc against the Clear Linux OS for Intel Architecture linux distribution
521 stars 29 forks source link

CIFS mount issues in 40330 #2995

Closed TiddaA closed 9 months ago

TiddaA commented 10 months ago

CIFS mounts fail for me in version 40330, in 40320it's still working. I'm getting the following in the journal:

Nov 09 23:05:14 clear2 systemd[1]: mnt-floradisk-backup.automount: Got automount request for /mnt/floradisk/backup, triggered by 2017 (mount.cifs) Nov 09 23:05:14 clear2 systemd[1]: Mounting mnt-floradisk-backup.mount... Nov 09 23:05:14 clear2 kernel: CIFS: Attempting to mount //floradisk/backup Nov 09 23:05:14 clear2 mount[2019]: mount error(126): Required key not available Nov 09 23:05:14 clear2 mount[2019]: Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg) Nov 09 23:05:14 clear2 systemd[1]: mnt-floradisk-backup.mount: Mount process exited, code=exited, status=32/n/a Nov 09 23:05:14 clear2 systemd[1]: mnt-floradisk-backup.mount: Failed with result 'exit-code'. Nov 09 23:05:14 clear2 systemd[1]: Failed to mount mnt-floradisk-backup.mount.

fenrus75 commented 10 months ago

any chance you can look in dmesg to see if there's something interesting there?

On Thu, Nov 9, 2023 at 2:58 PM TiddaA @.***> wrote:

CIFS mounts fail for me in version 40330, in 40320it's still working. I'm getting the following in the journal:

Nov 09 23:05:14 clear2 systemd[1]: mnt-floradisk-backup.automount: Got automount request for /mnt/floradisk/backup, triggered by 2017 (mount.cifs) Nov 09 23:05:14 clear2 systemd[1]: Mounting mnt-floradisk-backup.mount... Nov 09 23:05:14 clear2 kernel: CIFS: Attempting to mount //floradisk/backup Nov 09 23:05:14 clear2 mount[2019]: mount error(126): Required key not available Nov 09 23:05:14 clear2 mount[2019]: Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg) Nov 09 23:05:14 clear2 systemd[1]: mnt-floradisk-backup.mount: Mount process exited, code=exited, status=32/n/a Nov 09 23:05:14 clear2 systemd[1]: mnt-floradisk-backup.mount: Failed with result 'exit-code'. Nov 09 23:05:14 clear2 systemd[1]: Failed to mount mnt-floradisk-backup.mount.

— Reply to this email directly, view it on GitHub https://github.com/clearlinux/distribution/issues/2995, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJ54FMBDGPBQZ4AFBY2OZDYDVNY5AVCNFSM6AAAAAA7FKBPXSVHI2DSMVQWIX3LMV43ASLTON2WKOZRHE4DMNJUGU2DANA . You are receiving this because you are subscribed to this thread.Message ID: @.***>

TiddaA commented 10 months ago

Not much of interest in dmesg: [ 39.867744] calling init_cifs+0x0/0xfc0 [cifs] @ 1978 [ 39.868048] Key type cifs.idmap registered [ 39.868164] initcall init_cifs+0x0/0xfc0 [cifs] returned 0 after 370 usecs [ 39.868443] CIFS: No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3.1.1), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3.1.1 (or even SMB3 or SMB2.1) specify vers=1.0 on mount. [ 39.912204] CIFS: Attempting to mount //floradisk/backup

This is the message I get when doing mount -a: $ sudo mount -a Couldn't chdir to /mnt/floradisk/backup: No such device

strangecargo commented 10 months ago

I'm having a similar issue in 40360 where SMB mounts that used to work now fail. I don't know when it last worked because this VM had been running without a reboot for several weeks and the mounts had been mounted the whole time:

/sbin/mount.cifs "//server/share" /mnt/blargle/ -o guest mount error(126): Required key not available Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)

Corresponding dmesg lines:

[ 1304.897163] CIFS: Attempting to mount //server/share [ 1304.904005] vers=2.0 mount not permitted when legacy dialects disabled [ 1304.912468] vers=1.0 (cifs) mount not permitted when legacy dialects disabled

The SMB host is a QNAP NAS configured to allow SMB versions between 2.0 and 3 (inclusive).

strangecargo commented 9 months ago

Any guidance on what I can do to fix or debug this? If I can't figure this out, I'm just going to have to move this workload off to another OS.

TiddaA commented 9 months ago

I switched to NFS to access my NAS as a mitigation.

fenrus75 commented 9 months ago

I turned the insecure-but-compatible kernel config on in the hope that would fix this...

On Mon, Nov 27, 2023, 22:37 TiddaA @.***> wrote:

I switched to NFS to access my NAS as a mitigation.

— Reply to this email directly, view it on GitHub https://github.com/clearlinux/distribution/issues/2995#issuecomment-1828656767, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJ54FJC6PDGZJHN23WN7KDYGUBZNAVCNFSM6AAAAAA7FKBPXSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRYGY2TMNZWG4 . You are receiving this because you commented.Message ID: @.***>

TiddaA commented 9 months ago

I tried again, but still the same error in the journal, "mount error(126): Required key not available".

strangecargo commented 9 months ago

I'm still running into the same issue in 40410. Should your changes be in that version?

I turned the insecure-but-compatible kernel config on in the hope that would fix this...

strangecargo commented 9 months ago

Seems to be working again in 40430.

TiddaA commented 9 months ago

I can confirm it is working again as well. Thanks team!