I have noticed that after upgrading from Core 13.2 to 13.3 I have issues moving files/folders from one subfolder to subfolder within the same dataset.
The move seems be to complete, but nothing is moved. I checked directly on TrueNAS too with SSH if there is a timing/caching issue over SMB.
The new location receives nothing and the old location keeps the file/folder as if nothing happened.
Copying instead of moving files/folders within the dataset does work (and then deleting the old one by hand works too)
I use a Mac (Sonoma) with SMB to connect to the dataset. I have no auxiliary parameters in the SMB service.
Is this a known issue with the latest SMB ?
Thanks.
Same here. mv works on samba share mounted from linux, but not macOS.
This appears to be a samba misconfiguration, but I’m having a hard time figuring out where is the smb4.conf is. The one in the obvious locations evidently isn’t used.
Oh, right. I forgot about that upstream samba default change between 4.15 and 4.19. We accounted for it in SCALE (defaulting to False), but not in13.3. I created a ticket for 13.3-U1.
Thanks for finding this solution. Glad I am not the only one having this issue though :-).
I saw in the bud report it has to do with SMB2 on macOS. Will check if I can force macOS to move to smb3 or 4.
Thank you for reporting this issue! This bug has been resolved in TrueNAS SCALE and is not planned to be back-ported to CORE. If this is a critical workflow issue for you, we would strongly advise promptly upgrading to TrueNAS SCALE.
