Samba share directory can't rename.

[makmillion]

Try disabling thumbnail generation (and deleting any thumbs.db files that already exist). That solved the problem for me.

I've had thumbnail generation disabled for years, but I appreciate the suggestion. I ran a search for thumbs.db and found a few from recent a recent sync, deleted them but the issue persists.

 

[makmillion]

I can also report that changing my drive my mapping from \\HOSTNAME\SHARE to \\IP.ADDRESS\SHARE has fixed the issue (so far, limited testing) for me. I could reproduce the issue 100% of the time before, and my first few tests after the change have been successful (no issue). Whether there's a non-zero chance of it still happening, I am not sure as I have not done enough testing. But at least it's no longer 100%!

Mine has gone back to doing this 100% of the time, with no changes made.

I also noticed that when I go to the shares tab and disable an SMB share, I can still access it from my Windows machine. In fact, if I manually disconnect (from Windows) and then map the drive again, it shows up and allows me to map the same share, and access everything within it {edit:} and with the SMB share disabled, I am able to modify file names again. What's happening here?

 

[smiffy885]

Was a solution ever found for this, restarting the Samba service everytime I need to rename a folder is a bit of a pain

 

[Mistar Muffin]

I shot @anodos a PM to hopefully set up a TeamViewer session about this. I can reproduce it easily and it has been driving me nuts for months.

 

[donky353]

I shot @anodos a PM to hopefully set up a TeamViewer session about this. I can reproduce it easily and it has been driving me nuts for months.

If you are not able to get anything to work I am also available to test with @andos any time

 

[anodos]

Recap of teamviewer session. There was a bug in Samba 4.17 (BlueFin) in which client requesting to open an alternate datastream would cause fd leak of open on parent dir, which was inserted into samba's per-process open files list (which is checked during rename attempt). This has been fixed as of TrueNAS 22.12.3.

 

[Mistar Muffin]

I can confirm that @anodos upgraded my smb daemon to the version that ships with 22.12.3 and the issue is fixed. I am still on 22.12.2, for now, though. Is anyone on 22.12.3 and still experiencing this issue?

 

[donky353]

I can also confirm the issue appears to be resolved in 22.12.3.3

 

[imvi]

Same here. I wanted to wait a bit, but since upgrading it never happened again. Thanks a lot for debugging it.

 

[filipe.nanclarez]

Hi...

I update to 22.12.3.3 last weekend as the @anodos said, but the problem still here...

How can'i help to solve?

 

[makmillion]

Hi...

I update to 22.12.3.3 last weekend as the @anodos said, but the problem still here...

How can'i help to solve?

The update fixed my issue, but only after restarting the smb service on my (Windows 11) laptop. If you haven't yet, try rebooting the machine you use to connect to your server.

 

[filipe.nanclarez]

The update fixed my issue, but only after restarting the smb service on my (Windows 11) laptop. If you haven't yet, try rebooting the machine you use to connect to your server.

Yes, i have a network here, so i made update on weekend. All clients computers is off when i made update.

Some users have this issue, and they all alread know if restart the machine, they can rename files.

But this workaround bump my IT Area with a lots of tickets.