© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Hi R. Diez,
You have probably been following the chatter on the upstream mailing list
discussion. I initially thought the patch didn't fix the issue, as when I mount
with wsize=16850, the issue still occurs [1], but it seems that the intent of
the patch is to only correct when the server specifies an incorrect wsize, and
to correct that instead [2].
[1] https:/
[2] https:/
Anyway, I have built you a test kernel that includes the patch, not from today,
but yesterday's corrected one [3] ontop of 6.5.0-15-generic for Jammy HWE.
[3] https:/
If you want to try it out on your system before it gets merged upstream, please
do, since your SMB server sends a incorrect wsize.
Please note this package is NOT SUPPORTED by Canonical, and is for TESTING
PURPOSES ONLY. ONLY Install in a dedicated test environment.
Instructions to install (On a Jammy system):
1) sudo add-apt-repository ppa:mruffell/
2) sudo apt update
3) sudo apt install linux-image-
4) sudo reboot
5) uname -rv
6.5.0-15-generic #15~22.
Perform your smb1 mount but without any wsize set, and then run:
$ sudo dmesg | tail
or just look at the end of dmesg in journalctl, and could you please
1) send the output of the lines with "CIFS:" at the start. I just want to see
if the strings "CIFS: VFS: wsize should be a multiple of 4096 (PAGE_SIZE)" and
"CIFS: VFS: wsize too small, reset to minimum ie PAGE_SIZE, usually 4096" are
there. and:
2) see if the issue is actually fixed by doing a test copy and looking with less.
In the meantime I will ask Steve if its worth just setting all wsize to multiples
of PAGE_SIZE regardless how it is set, since a partial one on the mount command
line will destroy your data anyway, and thats not useful.
Thanks!
Matthew