Mathew Moore
2022-May-05 17:32 UTC
[Samba] Upgraded to Ubuntu 22.04 LTS. Kernal Panic when transferring large numbers of files from windows machine to samba-share
Hi All, new to the maillist. Any assistance appreciated. Please advise if I should send this elsewhere :) System: Samba domain member, samba-share. ext4 filesystem, MDADM raid 6. ~400TB. 128GB mem. System was stable on Ubuntu 20.04. Unstable following upgrade to 22.04 (kernel version 5.15) To reproduce kernel error, copy thousands of files (~1tb of data) to samba-share from any windows computer. Kernel error thrown, smbd process is unresponsive and cannot be killed, file transfer stops, the mounted drive freezes (directory operations including ls,mv,cp on the mount are not possible) and the system needs to be hard-rebooted. Quite an unhappy outcome :) I cannot reproduce the error copying via nfs or copying files on the drive itself. Single files or small transfers proceed without error. Filesystem passes fsck. Any assistance would be appreciated, I'm way out of my depth here :) Happy to assist in tracking this down. Pls let me know. Kernel error and smb.conf follows....... Regards, Mat *kern.log* May 3 16:48:05 nas kernel: [31727.490899] ------------[ cut here ]------------ May 3 16:48:05 nas kernel: [31727.490906] kernel BUG at fs/ext4/xattr.c:2071! May 3 16:48:05 nas kernel: [31727.490920] invalid opcode: 0000 [#1] SMP PTI May 3 16:48:05 nas kernel: [31727.490927] CPU: 26 PID: 22593 Comm: smbd Not tainted 5.15.0-27-generic #28-Ubuntu May 3 16:48:05 nas kernel: [31727.490934] Hardware name: Supermicro SSG-6048R-E1CR60L/X10DSC+, BIOS 3.2 11/19/2019 May 3 16:48:05 nas kernel: [31727.490937] RIP: 0010:ext4_xattr_block_set+0xbba/0xbd0 May 3 16:48:05 nas kernel: [31727.490953] Code: c7 45 8c f4 ff ff ff eb b4 48 8b 7d 90 48 c7 c1 7f 12 e1 b7 ba 2d 08 00 00 48 c7 c6 d0 3c a5 b7 e8 9b 6f ff ff e9 a5 fe ff ff <0f> 0b e8 0f d8 89 00 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 May 3 16:48:05 nas kernel: [31727.490958] RSP: 0018:ffffbf548ba6fa50 EFLAGS: 00010203 May 3 16:48:05 nas kernel: [31727.490965] RAX: 0000000000000002 RBX: ffff9a914460ed80 RCX: ffffffffb7e0a8e7 May 3 16:48:05 nas kernel: [31727.490970] RDX: 0000000000000099 RSI: 0000000000000000 RDI: 000000000003cda0 May 3 16:48:05 nas kernel: [31727.490973] RBP: ffffbf548ba6fb00 R08: ffff9a9167c4cf08 R09: 0000000000000000 May 3 16:48:05 nas kernel: [31727.490977] R10: ffff9a81db1e1120 R11: ffff9a92046b8ff0 R12: 0000000000000000 May 3 16:48:05 nas kernel: [31727.490980] R13: ffff9a820b1dd3c8 R14: 00000002f3798000 R15: 0000000000000000 May 3 16:48:05 nas kernel: [31727.490984] FS: 00007f3491bc9a40(0000) GS:ffff9a913fb80000(0000) knlGS:0000000000000000 May 3 16:48:05 nas kernel: [31727.490988] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 May 3 16:48:05 nas kernel: [31727.490992] CR2: 000055573b9a2b78 CR3: 000000110ca1c002 CR4: 00000000003706e0 May 3 16:48:05 nas kernel: [31727.490997] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 May 3 16:48:05 nas kernel: [31727.491000] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 May 3 16:48:05 nas kernel: [31727.491003] Call Trace: May 3 16:48:05 nas kernel: [31727.491007] <TASK> May 3 16:48:05 nas kernel: [31727.491010] ? jbd2_journal_get_write_access+0x43/0x90 May 3 16:48:05 nas kernel: [31727.491022] ext4_xattr_set_handle+0x487/0x620 May 3 16:48:05 nas kernel: [31727.491032] __ext4_set_acl+0xc1/0x130 May 3 16:48:05 nas kernel: [31727.491038] ext4_init_acl+0xe8/0x160 May 3 16:48:05 nas kernel: [31727.491043] __ext4_new_inode+0xf60/0x14e0 May 3 16:48:05 nas kernel: [31727.491048] ? path_parentat+0x4c/0x90 May 3 16:48:05 nas kernel: [31727.491057] ? __find_next_entry+0x144/0x180 May 3 16:48:05 nas kernel: [31727.491067] ext4_mkdir+0x157/0x330 May 3 16:48:05 nas kernel: [31727.491075] vfs_mkdir+0x142/0x200 May 3 16:48:05 nas kernel: [31727.491097] do_mkdirat+0x120/0x140 May 3 16:48:05 nas kernel: [31727.491102] __x64_sys_mkdirat+0x51/0x70 May 3 16:48:05 nas kernel: [31727.491105] do_syscall_64+0x5c/0xc0 May 3 16:48:05 nas kernel: [31727.491113] ? exit_to_user_mode_prepare+0x37/0xb0 May 3 16:48:05 nas kernel: [31727.491120] ? syscall_exit_to_user_mode+0x27/0x50 May 3 16:48:05 nas kernel: [31727.491124] ? __x64_sys_getxattr+0x24/0x30 May 3 16:48:05 nas kernel: [31727.491132] ? do_syscall_64+0x69/0xc0 May 3 16:48:05 nas kernel: [31727.491137] entry_SYSCALL_64_after_hwframe+0x44/0xae May 3 16:48:05 nas kernel: [31727.491143] RIP: 0033:0x7f3495e1463b May 3 16:48:05 nas kernel: [31727.491147] Code: 73 01 c3 48 8b 0d f5 47 10 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa b8 02 01 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c5 47 10 00 f7 d8 64 89 01 48 May 3 16:48:05 nas kernel: [31727.491151] RSP: 002b:00007ffe0f0e0b58 EFLAGS: 00000206 ORIG_RAX: 0000000000000102 May 3 16:48:05 nas kernel: [31727.491154] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f3495e1463b May 3 16:48:05 nas kernel: [31727.491157] RDX: 00000000000001ed RSI: 000055573b959e00 RDI: 0000000000000009 May 3 16:48:05 nas kernel: [31727.491159] RBP: 000055573b9532a0 R08: 000055573b992950 R09: 000055573b9a1ad0 May 3 16:48:05 nas kernel: [31727.491161] R10: 000000003b7c74ed R11: 0000000000000206 R12: 000055573b995c10 May 3 16:48:05 nas kernel: [31727.491164] R13: 000055573b97b2f0 R14: 000055573b968020 R15: 000055573b959cc0 May 3 16:48:05 nas kernel: [31727.491167] </TASK> May 3 16:48:05 nas kernel: [31727.491169] Modules linked in: tls intel_rapl_msr intel_rapl_common sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel ipmi_ssif kvm rapl intel_cstate joydev input_leds mei_me mei ioatdma acpi_ipmi ipmi_si acpi_power_meter acpi_pad mac_hid sch_fq_codel ipmi_devintf ipmi_msghandler msr dm_multipath parport_pc scsi_dh_rdac scsi_dh_emc ppdev scsi_dh_alua lp parport nfsd nfs_acl lockd auth_rpcgss grace sunrpc ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid0 multipath linear raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 ses enclosure ast i2c_algo_bit drm_vram_helper drm_ttm_helper ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops cec crct10dif_pclmul crc32_pclmul rc_core ghash_clmulni_intel ixgbe aesni_intel hid_generic usbhid xfrm_algo crypto_simd dca mdio mpt3sas cryptd i2c_i801 hid drm lpc_ich ahci i2c_smbus raid_class libahci scsi_transport_sas wmi May 3 16:48:05 nas kernel: [31727.491266] ---[ end trace 08938172912ffac3 ]--- May 3 16:48:05 nas kernel: [31727.554371] RIP: 0010:ext4_xattr_block_set+0xbba/0xbd0 May 3 16:48:05 nas kernel: [31727.554379] Code: c7 45 8c f4 ff ff ff eb b4 48 8b 7d 90 48 c7 c1 7f 12 e1 b7 ba 2d 08 00 00 48 c7 c6 d0 3c a5 b7 e8 9b 6f ff ff e9 a5 fe ff ff <0f> 0b e8 0f d8 89 00 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 May 3 16:48:05 nas kernel: [31727.554382] RSP: 0018:ffffbf548ba6fa50 EFLAGS: 00010203 May 3 16:48:05 nas kernel: [31727.554385] RAX: 0000000000000002 RBX: ffff9a914460ed80 RCX: ffffffffb7e0a8e7 May 3 16:48:05 nas kernel: [31727.554387] RDX: 0000000000000099 RSI: 0000000000000000 RDI: 000000000003cda0 May 3 16:48:05 nas kernel: [31727.554389] RBP: ffffbf548ba6fb00 R08: ffff9a9167c4cf08 R09: 0000000000000000 May 3 16:48:05 nas kernel: [31727.554391] R10: ffff9a81db1e1120 R11: ffff9a92046b8ff0 R12: 0000000000000000 May 3 16:48:05 nas kernel: [31727.554393] R13: ffff9a820b1dd3c8 R14: 00000002f3798000 R15: 0000000000000000 May 3 16:48:05 nas kernel: [31727.554395] FS: 00007f3491bc9a40(0000) GS:ffff9a913fb80000(0000) knlGS:0000000000000000 May 3 16:48:05 nas kernel: [31727.554398] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 May 3 16:48:05 nas kernel: [31727.554400] CR2: 000055573b9a2b78 CR3: 000000110ca1c002 CR4: 00000000003706e0 May 3 16:48:05 nas kernel: [31727.554402] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 May 3 16:48:05 nas kernel: [31727.554404] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 *smb.conf* [global] workgroup = INT security = ADS realm = INT.RESEARCHDX.COM winbind refresh tickets = Yes store dos attributes = Yes dedicated keytab file = /etc/krb5.keytab kerberos method = secrets and keytab winbind use default domain = yes #RID Backend idmap config * : backend = tdb idmap config * : range = 3000-7999 idmap config SAMDOM : backend = rid idmap config SAMDOM : range = 10000-999999 # Template settings for login shell and home directory template shell = /bin/bash template homedir = /home/%U #Map domain admin to root username map = /etc/samba/user.map [NGS] path = /mnt/MyStorage/Storage/ read only = no vfs objects = acl_xattr map acl inherit = Yes Regards, Mathew Moore, PhD Principal, ResearchDx
Jeremy Allison
2022-May-05 17:36 UTC
[Samba] Upgraded to Ubuntu 22.04 LTS. Kernal Panic when transferring large numbers of files from windows machine to samba-share
On Thu, May 05, 2022 at 10:32:09AM -0700, Mathew Moore via samba wrote:>Hi All, new to the maillist. Any assistance appreciated. Please advise >if I should send this elsewhere :) > >System: Samba domain member, samba-share. ext4 filesystem, MDADM raid 6. >~400TB. 128GB mem. > > >System was stable on Ubuntu 20.04. Unstable following upgrade to >22.04 (kernel >version 5.15) >To reproduce kernel error, copy thousands of files (~1tb of data) to >samba-share from any windows computer. Kernel error thrown, smbd process >is unresponsive and cannot be killed, file transfer stops, the mounted >drive freezes (directory operations including ls,mv,cp on the mount are not >possible) and the system needs to be hard-rebooted. Quite an unhappy >outcome :) > >I cannot reproduce the error copying via nfs or copying files on the drive >itself. > >Single files or small transfers proceed without error. >Filesystem passes fsck. > >Any assistance would be appreciated, I'm way out of my depth here :) >Happy to assist in tracking this down. Pls let me know. > >Kernel error and smb.conf follows.......Kernel errors in ext4 can't be fixed directly in Samba I'm afraid. You'll need to report this to the Linux kernel mailing lists. When you get the kernel error can you get a stack backtrace to see what smbd was doing at the time ?
Good evening: I've updated my Samba RPM building tools to support 4.16.1, over at https://github.com/nkadel/samba4repo/ .It's passing my limited tests, yay. Note that this has active directory features enabled, unlike the standard RHEL versions, It also uses Heimdal Kerberos, rather than Fedora's election to use the experimental MIT Kerberos support. Nico Kadel-Garcia