Hello team,

let me give you some context. I have a share named "Peliculas".

If I try to create a folder, create a file or copy a file inside that share I get an error.

For example If I try to create a folder:

On mac:

Using Windows:

(the text its on spanish and said: "The file '<%1 NULL:NameDest>' is too big for the destination filesystem.)

However, this error solves if I create a folder named "Peliculas" on the patch /mnt/cache/.

Once I do this, I can use the share normally until the next 'mover' process runs. Than, I'm stuck with the same issue all over again.
BTW, It doesn't matter if the folder "Peliculas" 's owner and group are root:root or nobody:users. It's the same for both cases.

I'm really confused about this one, I do not know what to do to be honest.

Any help will be appreciated.

Thank you in advance.

tower-diagnostics-20260518-1958.zip

Edited May 18May 18 by Juanzilla

You are likely to get better informed feedback if you attach your system’s diagnostics (with everything in the one zip file) to your next post in this thread. It is always a good idea when asking questions to supply your diagnostics so we can see details of your system, how you have things configured, and the current syslog.

hello @itimpi ,

Thank you for your suggestion/correction.

I just added the diagnostics file to the mail post.

Hope it could help.
Again thank you!

Looks like root:root for the owner:group on the share. you will want to change this to nobody:users instead. You can do it from the built in file-manager or typing in chown nobody:users /mnt/cache/Peliculas in the terminal.

Edited May 18May 18 by MowMdown

Hello @MowMdown

thank you for your comment. As I mentioned on the original post, i try with both root:root and nobody:users with both the same issue...
In fact, in order to correct all the groups:users possible issues, I ran the tool --> new perissions feature with the same results.

BTW, I also noticed that I have two shares set on the shares GUI (droppy and dvr). These shares are no longer needed. When I try to delete them, the GUI start running but they do not do anything (not even an error).

If I check the /mnt/cache the directories are there, however if i check the /mnt/user0 the directories are not there

So, If I have to guess, it seems like for some reason the directories in my cache drive are not in sync with my array (or something on that nature).

Something its out of sync and I can't put my finger on it.

Edited May 18May 18 by Juanzilla

12 hours ago, Juanzilla said:

If I check the /mnt/cache the directories are there, however if i check the /mnt/user0 the directories are not there

This would be expected as /mnt/user0 is for shares that only have files/folders on the main array disks and not on any pools (e.g. ‘cache’),

The syslog has lots of errors relating to problems with datasets on the ‘cache’ pool. Maybe someone who understands ZFS file systems will know the cause and what remedial action to take.

Like Itimpi said, /mnt/user0 is a special FUSE path that just represents all your Array Disk shares & data w/o the cache(pools) data being included. You should generally ignore it unless you have a special use case for writing to the array only manually.

Edited May 19May 19 by MowMdown

Thank you guys for your answers.
I decided to move all the content to the array and remove the cache for a wild. I thought that this could force sync process between the cache and the array.... Unfortunately, while I was in the middle of moving everything out of the cache, my main HDD decided to die... So, I needed to buy a new hdd and replace it... All of this process took me a couple of days but at the end of this whole process, it ended up working in my favor since the cache is now in sync...

Thank you again for your help!