Two folders in pool appear corrupt

TrueNAS-SCALE-23.10.2

Hi, all, I seem to have messed up an SMB share. Two folders in it have gotten corrupted, with names like “(A Document Being ~AUhelperService 2)”. They have a single subfolder; one is “.AU.SDd3T.nosync”. Under those subfolders there’s nothing.

All other data in the pool appears present.

zpool status -v shows no errors.

I have two connections to the NAS, one ethernet, one fiber. Normally use the faster fiber connection, but had tried to connect via ethernet instead but it was not connecting for some reason, so reverted to the fiber, and that’s when I first noticed the corrupted folder names.

It’s possible I tried to connect both via ethernet and fiber, don’t recall, I was troubleshooting another issue on the machine that connects to the NAS.

There have been no power outages recently. I did reboot the server thinking I was having a connection issue, but may not have needed to.

Alas, I do not have an available snapshot.

What would be the best way to try and get these two folders back? I know the data is in there somewhere, just don’t know how to ask TrueNas to recover it.

The last scrub occurred yesterday (Sunday) on its regular schedule.

Am running another scrub but since status is not showing any errors am not sure what it might find.

Does it appear that way on the local filesystem or only through the SMB protocol? If it’s the latter case then it’s probably just the name mangling algorithm adjusting the name so that SMB clients can actually read it (e.g. the name contains invalid characters).

Yeah, sorry, should have mentioned that. It’s the same way on the local filesystem, SSH’d into the NAS.

Also, not sure if this has any bearing, but viewed from the workstation an ls -l shows the two corrupted folder names before the normal . and … that you’d normally see first. On the server, ls -la shows the same.

Could you post the screenshot of that ls command? Would be easier if we can actually see it visually.

1 Like

Here you go, but I think I’m OK. Those spurious folders are old, there’s no actual data loss. Just got cornfused for a bit. Sorry to have panicked!

It wouldn’t let me embed the screenshot so here’s a partial text output from ls -la:

total 192
drwx------ 1 osxtra 16384 May 19 11:04 ‘(A Document Being Saved By AUHelperService 2)’
drwx------ 1 osxtra 16384 Aug 26 2024 ‘(A Document Being Saved By AUHelperService)’
drwx------ 1 osxtra 16384 Jul 14 10:25 .
drwx------ 1 osxtra 16384 Sep 25 2024 …
drwx------ 1 osxtra 16384 Sep 23 2023 Apps
drwx------ 1 osxtra 16384 Jul 13 14:28 Downloads
drwx------ 1 osxtra 16384 Nov 21 2024 Junk

Oh, and here’s the subfolder from “(A Document Being Saved By AUHelperService)”

total 48
drwx------ 1 osxtra 16384 Aug 26 2024 .
drwx------ 1 osxtra 16384 Jul 14 10:25 …
drwx------ 1 osxtra 16384 Aug 26 2024 .AU.6iCId

This doesn’t look like corruption. This looks like maybe MacOS failed to extract a zipped file into the SMB share (possibly due to an invalid file name).