Confusing Permissions Issue

[Chamrajnagar]

I recently upgraded to TrueNAS 12.0-U4 from FreeNAS 11.3 after my boot drive died.

I have three CIFS shares which I imported. I can see all three on my Windows machine, but I can only write to two of them. I can only read wafflefries.

The TrueNAS settings are identical between the three. I am signed into the same account (user josh which I created on TrueNAS) for all on Windows. I have tried deleting all my TrueNAS/FreeNAS credentials in Windows but the issue is still present.

I'm not a TrueNAS expert so not really sure where to look. Suggestions appreciated.

Thanks!

 

[JohnDigital]

who owns the dataset /mnt/wafflefries ? What are its permissions?

 

[Chamrajnagar]

who owns the dataset /mnt/wafflefries ? What are its permissions?

Hi John, sorry for the delayed reply. I believe it is owned by root, although I'm not sure how to check this. If I go to user quotas from the dataset, root is the only user listed.

 

[Chamrajnagar]

It seems I can't access any of the three shares now, though I haven't changed anything. Is there an option to reset a dataset to its defaults? Maybe I need to start with a clean slate.

 

[Chamrajnagar]

I think my NAS box had bit hit with a small power blip, taking the shares offline. Restarting the system resolved the most recent issue, and I was back to having full access to two of the shares. I noticed a small blip again yesterday, and noticed the NAS went offline again. I have a UPS on the way to help mitigate any power supply issues in the future.

To address the main issue of inconsistent permissions, I resorted to creating new datasets and moving all my data around to start fresh. This time around I made sure not to create any shares mounted on the root dataset. I also set the 'Share Type' to SMB when creating the shares, as I read it's important to do this on creation as it can't be changed after. It's possible some or all of my prior datasets were left set to the default on creation.

With this new setup, things seem to be working more smoothly. I am almost finished transferring my data to the new shares, then I can delete the old ones.

 

[Chamrajnagar]

My pools & datasets now look like this:

Is it bad practice to have nested datasets with the same name?

 

[Chamrajnagar]

I couldn't find any info about whether it was considered bad practice to have nested datasets with the same name, so I erred on the safe side and created new ones.

I truly don't know what was wrong with my original datasets and shares, but creating new ones with the same settings seems to have resolved things for now.