Unraid-arr Posted February 9, 2023 Share Posted February 9, 2023 Quote Feb 9 13:23:17 Tower smbd[22785]: [2023/02/09 13:23:17.454400, 0] ../../source3/smbd/close.c:1485(close_directory) Feb 9 13:23:17 Tower smbd[22785]: Could not close dir! fname=complete, fd=32, err=116=Stale file handle Feb 9 13:23:17 Tower smbd[22785]: [2023/02/09 13:23:17.505657, 0] ../../source3/smbd/close.c:1485(close_directory) Feb 9 13:23:17 Tower smbd[22785]: Could not close dir! fname=incomplete, fd=35, err=116=Stale file handle Feb 9 13:23:26 Tower smbd[22785]: [2023/02/09 13:23:26.346455, 0] ../../source3/smbd/close.c:1397(close_directory) Feb 9 13:23:26 Tower smbd[22785]: close_directory: Could not get share mode lock for incomplete Feb 9 13:23:26 Tower smbd[22785]: [2023/02/09 13:23:26.346526, 0] ../../source3/smbd/fd_handle.c:39(fd_handle_destructor) Feb 9 13:23:26 Tower smbd[22785]: PANIC: assert failed at ../../source3/smbd/fd_handle.c(39): (fh->fd == -1) || (fh->fd == AT_FDCWD) Feb 9 13:23:26 Tower smbd[22785]: [2023/02/09 13:23:26.346543, 0] ../../lib/util/fault.c:173(smb_panic_log) Feb 9 13:23:26 Tower smbd[22785]: =============================================================== Feb 9 13:23:26 Tower smbd[22785]: [2023/02/09 13:23:26.346560, 0] ../../lib/util/fault.c:174(smb_panic_log) Feb 9 13:23:26 Tower smbd[22785]: INTERNAL ERROR: assert failed: (fh->fd == -1) || (fh->fd == AT_FDCWD) in pid 22785 (4.17.3) Feb 9 13:23:26 Tower smbd[22785]: [2023/02/09 13:23:26.346573, 0] ../../lib/util/fault.c:178(smb_panic_log) Feb 9 13:23:26 Tower smbd[22785]: If you are running a recent Samba version, and if you think this problem is not yet fixed in the latest versions, please consider reporting this bug, see https://wiki.samba.org/index.php/Bug_Reporting Feb 9 13:23:26 Tower smbd[22785]: [2023/02/09 13:23:26.346587, 0] ../../lib/util/fault.c:183(smb_panic_log) Feb 9 13:23:26 Tower smbd[22785]: =============================================================== Feb 9 13:23:26 Tower smbd[22785]: [2023/02/09 13:23:26.346614, 0] ../../lib/util/fault.c:184(smb_panic_log) Feb 9 13:23:26 Tower smbd[22785]: PANIC (pid 22785): assert failed: (fh->fd == -1) || (fh->fd == AT_FDCWD) in 4.17.3 Feb 9 13:23:26 Tower smbd[22785]: [2023/02/09 13:23:26.347071, 0] ../../lib/util/fault.c:292(log_stack_trace) Feb 9 13:23:26 Tower smbd[22785]: BACKTRACE: 38 stack frames: Feb 9 13:23:26 Tower smbd[22785]: #0 /usr/lib64/libgenrand-samba4.so(log_stack_trace+0x2e) [0x153a33c0764e] Feb 9 13:23:26 Tower smbd[22785]: #1 /usr/lib64/libgenrand-samba4.so(smb_panic+0x9) [0x153a33c078a9] Feb 9 13:23:26 Tower smbd[22785]: #2 /usr/lib64/libsmbd-base-samba4.so(+0x4d10b) [0x153a33fe810b] Feb 9 13:23:26 Tower smbd[22785]: #3 /usr/lib64/libtalloc.so.2(+0x44df) [0x153a33bb74df] Feb 9 13:23:26 Tower smbd[22785]: #4 /usr/lib64/libsmbd-base-samba4.so(file_free+0xd6) [0x153a33ff52e6] Feb 9 13:23:26 Tower smbd[22785]: #5 /usr/lib64/libsmbd-base-samba4.so(close_file_free+0x29) [0x153a34025d49] Feb 9 13:23:26 Tower smbd[22785]: #6 /usr/lib64/libsmbd-base-samba4.so(+0x5d046) [0x153a33ff8046] Feb 9 13:23:26 Tower smbd[22785]: #7 /usr/lib64/libsmbd-base-samba4.so(+0x5d1ce) [0x153a33ff81ce] Feb 9 13:23:26 Tower smbd[22785]: #8 /usr/lib64/libsmbd-base-samba4.so(files_forall+0x19) [0x153a33ff4119] Feb 9 13:23:26 Tower smbd[22785]: #9 /usr/lib64/libsmbd-base-samba4.so(file_close_user+0x3d) [0x153a33ff425d] Feb 9 13:23:26 Tower smbd[22785]: #10 /usr/lib64/libsmbd-base-samba4.so(smbXsrv_session_logoff+0x4d) [0x153a3407100d] Feb 9 13:23:26 Tower smbd[22785]: #11 /usr/lib64/libsmbd-base-samba4.so(+0xd6445) [0x153a34071445] Feb 9 13:23:26 Tower smbd[22785]: #12 /usr/lib64/libdbwrap-samba4.so(+0x5d18) [0x153a338e9d18] Feb 9 13:23:26 Tower smbd[22785]: #13 /usr/lib64/libdbwrap-samba4.so(+0x5f3a) [0x153a338e9f3a] Feb 9 13:23:26 Tower smbd[22785]: #14 /usr/lib64/libdbwrap-samba4.so(dbwrap_traverse+0x7) [0x153a338e7f67] Feb 9 13:23:26 Tower smbd[22785]: #15 /usr/lib64/libsmbd-base-samba4.so(smbXsrv_session_logoff_all+0x5b) [0x153a340717fb] Feb 9 13:23:26 Tower smbd[22785]: #16 /usr/lib64/libsmbd-base-samba4.so(+0xdca0b) [0x153a34077a0b] Feb 9 13:23:26 Tower smbd[22785]: #17 /usr/lib64/libsmbd-base-samba4.so(smbd_reinit_after_fork+0) [0x153a34077ff0] Feb 9 13:23:26 Tower smbd[22785]: #18 /usr/lib64/libsmbd-shim-samba4.so(exit_server_cleanly+0x14) [0x153a33c0c284] Feb 9 13:23:26 Tower smbd[22785]: #19 /usr/lib64/libsmbd-base-samba4.so(smbd_server_connection_terminate_ex+0x4d6) [0x153a3404d4c6] Feb 9 13:23:26 Tower smbd[22785]: #20 /usr/lib64/libtevent.so.0(tevent_common_invoke_fd_handler+0x91) [0x153a33bca791] Feb 9 13:23:26 Tower smbd[22785]: #21 /usr/lib64/libtevent.so.0(+0xec87) [0x153a33bd0c87] Feb 9 13:23:26 Tower smbd[22785]: #22 /usr/lib64/libtevent.so.0(+0xcd77) [0x153a33bced77] Feb 9 13:23:26 Tower smbd[22785]: #23 /usr/lib64/libtevent.so.0(_tevent_loop_once+0x91) [0x153a33bc9b61] Feb 9 13:23:26 Tower smbd[22785]: #24 /usr/lib64/libtevent.so.0(tevent_common_loop_wait+0x1b) [0x153a33bc9e3b] Feb 9 13:23:26 Tower smbd[22785]: #25 /usr/lib64/libtevent.so.0(+0xcd17) [0x153a33bced17] Feb 9 13:23:26 Tower smbd[22785]: #26 /usr/lib64/libsmbd-base-samba4.so(smbd_process+0x817) [0x153a3403ece7] Feb 9 13:23:26 Tower smbd[22785]: #27 /usr/sbin/smbd(+0xb090) [0x55641875f090] Feb 9 13:23:26 Tower smbd[22785]: #28 /usr/lib64/libtevent.so.0(tevent_common_invoke_fd_handler+0x91) [0x153a33bca791] Feb 9 13:23:26 Tower smbd[22785]: #29 /usr/lib64/libtevent.so.0(+0xec87) [0x153a33bd0c87] Feb 9 13:23:26 Tower smbd[22785]: #30 /usr/lib64/libtevent.so.0(+0xcd77) [0x153a33bced77] Feb 9 13:23:26 Tower smbd[22785]: #31 /usr/lib64/libtevent.so.0(_tevent_loop_once+0x91) [0x153a33bc9b61] Feb 9 13:23:26 Tower smbd[22785]: #32 /usr/lib64/libtevent.so.0(tevent_common_loop_wait+0x1b) [0x153a33bc9e3b] Feb 9 13:23:26 Tower smbd[22785]: #33 /usr/lib64/libtevent.so.0(+0xcd17) [0x153a33bced17] Feb 9 13:23:26 Tower smbd[22785]: #34 /usr/sbin/smbd(main+0x1489) [0x55641875c259] Feb 9 13:23:26 Tower smbd[22785]: #35 /lib64/libc.so.6(+0x23177) [0x153a339d4177] Feb 9 13:23:26 Tower smbd[22785]: #36 /lib64/libc.so.6(__libc_start_main+0x85) [0x153a339d4235] Feb 9 13:23:26 Tower smbd[22785]: #37 /usr/sbin/smbd(_start+0x21) [0x55641875cb31] Feb 9 13:23:26 Tower smbd[22785]: [2023/02/09 13:23:26.347389, 0] ../../source3/lib/dumpcore.c:315(dump_core) Feb 9 13:23:26 Tower smbd[22785]: dumping core in /var/log/samba/cores/smbd Feb 9 13:23:26 Tower smbd[22785]: Please help me if someone knows what is going on here. Thanks in Advance. Quote Link to comment
hanmaan Posted February 11, 2023 Share Posted February 11, 2023 You're not the only one. I'm getting this too. Quote Link to comment
trurl Posted February 11, 2023 Share Posted February 11, 2023 attach diagnostics to your NEXT post in this thread Quote Link to comment
Unraid-arr Posted February 12, 2023 Author Share Posted February 12, 2023 9 hours ago, trurl said: attach diagnostics to your NEXT post in this thread Here you go. Thanks for reminding. Sorry I missed it earlier.🙂 I hope you can help me. Cheers! zeus-diagnostics-20230211-2238.zip Quote Link to comment
Unraid-arr Posted February 19, 2023 Author Share Posted February 19, 2023 On 2/11/2023 at 1:05 PM, trurl said: attach diagnostics to your NEXT post in this thread Hi @trurl, If it is possible to help with this issue, that would be highly appreciated. 😊 I attached the logs in my last message. Cheers! Quote Link to comment
trurl Posted February 19, 2023 Share Posted February 19, 2023 I don't know what those smbd entries in syslog are. Is it causing any actual problems? Quote Link to comment
Unraid-arr Posted February 19, 2023 Author Share Posted February 19, 2023 2 hours ago, trurl said: I don't know what those smbd entries in syslog are. Is it causing any actual problems? When I try to browse the shares remotely and delete any folders containing files, it only deletes a few files within the folder and stops. So then I have to delete a folder over and over again, to actually delete everything within it. Then once everything within the folder is deleted, there is almost always the empty folder left which I have to delete at last. Cheers! Quote Link to comment
trurl Posted February 19, 2023 Share Posted February 19, 2023 16 minutes ago, Shomil Saini said: browse the shares remotely What is the remote client? Quote Link to comment
Unraid-arr Posted February 19, 2023 Author Share Posted February 19, 2023 5 hours ago, trurl said: What is the remote client? Cx File Explorer on Android Phone. Cheers! Quote Link to comment
Solution trurl Posted February 19, 2023 Solution Share Posted February 19, 2023 1 Quote Link to comment
Unraid-arr Posted February 20, 2023 Author Share Posted February 20, 2023 21 hours ago, trurl said: Thanks for this link. As it stands there is an open issue, however the workaround is gonna have to do it for now. Hope this gets fixed soon. Cheers! Quote Link to comment
Neha Posted September 26, 2023 Share Posted September 26, 2023 On 2/21/2023 at 1:41 AM, Unraid-arr said: Thanks for this link. As it stands there is an open issue, however the workaround is gonna have to do it for now. Hope this gets fixed soon. Cheers! I am having the same issue on debian 12. What exactly is the workaround? Quote Link to comment
Unraid-arr Posted September 26, 2023 Author Share Posted September 26, 2023 (edited) 6 hours ago, Neha said: I am having the same issue on debian 12. What exactly is the workaround? Hi Neha, In Unraid v6.11.5 I use the /mnt/disk*/ paths rather than going through /mnt/user/shares which solves my issue for now. Here is the link to solution from Unraid admins. >>>Forum Discussion<<< I am not sure about Debian specifically. Please elaborate on the issue you are having. Cheers! Edited September 26, 2023 by Unraid-arr Quote Link to comment
Neha Posted September 27, 2023 Share Posted September 27, 2023 (edited) 10 hours ago, Unraid-arr said: Hi Neha, In Unraid v6.11.5 I use the /mnt/disk*/ paths rather than going through /mnt/user/shares which solves my issue for now. Here is the link to solution from Unraid admins. >>>Forum Discussion<<< I am not sure about Debian specifically. Please elaborate on the issue you are having. Cheers! I am running a raspberrypi 4b on debian 12 os. If I delete a folder or file via any file explorer android app, it gives an error and then the file or folder gets deleted. If a folder has more than one file then each file has to be deleted first. This was not happening when I was on debian 11. The OS variant I have installed is only Terminal based no GUI. sudo chown -R server:server /media/Server sudo chmod 0777 -R /media/Server File permissions are all set to 0777 and (user and group) are for user server. Below is the mounting string from /etc/fstab on the server UUID=xxxxxxxxx /media/Server ntfs defaults,auto,users,uid=998,gid=992,rw,nofail 0 0 Below is the smb.conf: [Server] path = /media/Server browseable = no read only = no valid users = server writeable = yes create mask=0777 directory mask=0777 So what should I change here for thr workaround to work? Kindly guide. Edited September 27, 2023 by Neha Quote Link to comment
Unraid-arr Posted September 27, 2023 Author Share Posted September 27, 2023 15 hours ago, Neha said: I am running a raspberrypi 4b on debian 12 os. If I delete a folder or file via any file explorer android app, it gives an error and then the file or folder gets deleted. If a folder has more than one file then each file has to be deleted first. This was not happening when I was on debian 11. The OS variant I have installed is only Terminal based no GUI. sudo chown -R server:server /media/Server sudo chmod 0777 -R /media/Server File permissions are all set to 0777 and (user and group) are for user server. Below is the mounting string from /etc/fstab on the server UUID=xxxxxxxxx /media/Server ntfs defaults,auto,users,uid=998,gid=992,rw,nofail 0 0 Below is the smb.conf: [Server] path = /media/Server browseable = no read only = no valid users = server writeable = yes create mask=0777 directory mask=0777 So what should I change here for thr workaround to work? Kindly guide. This would be better asked on Linux forums or subreddits, however I will try to answer. So, from the info you provided it looks like you will try to access the share as: \\rpi-ipaddress\media\Server however, workaround for unraid is to use drive not share folders, so something equivalent in linux should be \\rpi-ipaddress\root\dev\disk\by-id so you would mount the root directory as share like so in smb.conf [rootshare] path= / comment= browseable= yes I may or maynot be correct in the exact path name however, the concept is that you want to access it via the drive not the shared folder. Hope I am making sense. Cheers! Quote Link to comment
Neha Posted September 28, 2023 Share Posted September 28, 2023 Thank you I will give this a try and let you know Quote Link to comment
Unraid-arr Posted October 4, 2023 Author Share Posted October 4, 2023 On 9/28/2023 at 2:27 AM, Neha said: Thank you I will give this a try and let you know Any updates? Quote Link to comment
.thumb.jpg.d74871f2737d625ddd6091e019824d83.jpg)
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.