Samba client freeze during write when using higher than vers=1.0
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Hello,
My issue is that whenever I try to write new files (copy or move) to my file server something in the samba client freezes and I can't do anything samba until the system is rebooted.
To get write access I mount with uid ie "sudo mount //server/share /mountpoint -o user=write,
When this happens the server is still happily serving files to other machines.
If I just read files everything works fine.
If I connect from a windows client there is no issue.
If I add "vers=1.0" everything works but transfers are really slow. Specifying version 3 produces a fail.
Trying the same operation (different hw) with Mint 18 Mate produces the same fault.
Trying the same operation (with "vers=3.0" set) using SuSE Leap 15.0 KDE live everything works as expected.
Both client and server are running fully updated, as of posting, bionic.
Using 'dmesg -w' too see what's going on I can see that there is a general protection fault somehow related to cifsd. I am however unable to tell if it is relevant to my issue, from kern.log:
Jan 9 21:03:49 ubnu kernel: [ 410.357213] general protection fault: 0000 [#1] SMP PTI
Jan 9 21:03:49 ubnu kernel: [ 410.357224] Modules linked in: cmac arc4 md4 nls_utf8 cifs ccm fscache rfcomm pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) thunderbolt bnep binfmt_misc nls_iso8859_1 snd_hda_codec_hdmi snd_soc_skl snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc snd_hda_
Jan 9 21:03:49 ubnu kernel: [ 410.357357] wmi_bmof snd_timer memstick intel_wmi_
Jan 9 21:03:49 ubnu kernel: [ 410.357447] CPU: 2 PID: 1822 Comm: cifsd Tainted: G OE 4.15.0-43-generic #46-Ubuntu
Jan 9 21:03:49 ubnu kernel: [ 410.357453] Hardware name: /NUC7i3BNB, BIOS BNKBL357.
Jan 9 21:03:49 ubnu kernel: [ 410.357468] RIP: 0010:prefetch_
Jan 9 21:03:49 ubnu kernel: [ 410.357474] RSP: 0018:ffffb16201
Jan 9 21:03:49 ubnu kernel: [ 410.357482] RAX: 0000000000000000 RBX: e90527c744fff71a RCX: 0000000000003ea9
Jan 9 21:03:49 ubnu kernel: [ 410.357488] RDX: 0000000000003ea8 RSI: e90527c744fff71a RDI: ffff9d7079255080
Jan 9 21:03:49 ubnu kernel: [ 410.357494] RBP: ffffb16201ae3da0 R08: ffff9d707ed2b650 R09: ffffb16201ae3db0
Jan 9 21:03:49 ubnu kernel: [ 410.357499] R10: ffffb16201ae3de8 R11: 0000000000000000 R12: 0000000001011200
Jan 9 21:03:49 ubnu kernel: [ 410.357505] R13: ffff9d7079255080 R14: ffff9d7016478c40 R15: ffff9d7079255080
Jan 9 21:03:49 ubnu kernel: [ 410.357512] FS: 000000000000000
Jan 9 21:03:49 ubnu kernel: [ 410.357519] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jan 9 21:03:49 ubnu kernel: [ 410.357525] CR2: 00007f0a2802d028 CR3: 000000003760a006 CR4: 00000000003606e0
Jan 9 21:03:49 ubnu kernel: [ 410.357530] Call Trace:
Jan 9 21:03:49 ubnu kernel: [ 410.357545] kmem_cache_
Jan 9 21:03:49 ubnu kernel: [ 410.357558] ? mempool_
Jan 9 21:03:49 ubnu kernel: [ 410.357570] ? wait_woken+
Jan 9 21:03:49 ubnu kernel: [ 410.357580] mempool_
Jan 9 21:03:49 ubnu kernel: [ 410.357590] mempool_
Jan 9 21:03:49 ubnu kernel: [ 410.357660] ? smb2_add_
Jan 9 21:03:49 ubnu kernel: [ 410.357709] cifs_small_
Jan 9 21:03:49 ubnu kernel: [ 410.357751] cifs_demultiple
Jan 9 21:03:49 ubnu kernel: [ 410.357762] ? __schedule+
Jan 9 21:03:49 ubnu kernel: [ 410.357777] kthread+0x121/0x140
Jan 9 21:03:49 ubnu kernel: [ 410.357815] ? cifs_handle_
Jan 9 21:03:49 ubnu kernel: [ 410.357827] ? kthread_
Jan 9 21:03:49 ubnu kernel: [ 410.357838] ? do_syscall_
Jan 9 21:03:49 ubnu kernel: [ 410.357847] ? SyS_exit_
Jan 9 21:03:49 ubnu kernel: [ 410.357859] ret_from_
Jan 9 21:03:49 ubnu kernel: [ 410.357866] Code: eb bb 49 8b 74 24 60 48 c7 c7 30 cd 0e a5 e8 93 b9 ea ff eb 90 90 0f 1f 44 00 00 55 48 85 f6 48 89 e5 74 14 48 63 47 20 48 01 c6 <48> 33 36 48 33 b7 40 01 00 00 0f 18 0e 5d c3 66 90 66 2e 0f 1f
Jan 9 21:03:49 ubnu kernel: [ 410.357991] RIP: prefetch_
Jan 9 21:03:49 ubnu kernel: [ 410.358063] ---[ end trace 9fca55019e520b64 ]---
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/pcmC1D0p: jerker 1682 F...m pulseaudio
/dev/snd/
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
HibernationDevice: RESUME=
InstallationDate: Installed on 2018-11-14 (197 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
IwConfig:
eno1 no wireless extensions.
lo no wireless extensions.
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=
ProcVersionSign
RelatedPackageV
linux-
linux-
linux-firmware 1.173.6
RfKill:
0: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
Tags: bionic wayland-session
Uname: Linux 4.15.0-50-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 05/16/2019
dmi.bios.vendor: Intel Corp.
dmi.bios.version: BNKBL357.
dmi.board.name: NUC7i3BNB
dmi.board.vendor: Intel Corporation
dmi.board.version: J22859-303
dmi.chassis.type: 3
dmi.modalias: dmi:bvnIntelCor
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https:/ /wiki.ubuntu. com/Bugs/ FindRightPackag e. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.
To change the source package that this bug is filed about visit https:/ /bugs.launchpad .net/ubuntu/ +bug/1811723/ +editstatus and add the package name in the text box next to the word Package.
[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]