seanmcg182
Dabbler
- Joined
- Feb 14, 2021
- Messages
- 18
Just creating a post for a solution I found to some weirdness in case anyone else needs it... I wrote the post while in the middle of transferring data for my solution in case it didn't work... but it did work, so I figured I'd share the original intended post, and my solution to it.
ISSUE:
To summarize my setup:
- XCP-ng is installed on the bare server.
- I have 32GB RAM and 8 vCPUs dedicated to TrueNAS (current version 13.0-U3, i updated from U2 seeing if I could fix this issue)
- I have a Dataset "Windows", with 6 Child Datasets "Documents", "Pictures" etc
- - I did this to allow for varied snapshot schedules.
- I have the "Windows" dataset shared via SMB, with open ACL, set recursively to all children.
I can access this share and all children PERFECTLY on my Windows 11 Desktop. Read, Write, whole 9 yards, no problems AT ALL.
However, I have another VM (Ubuntu 20.04) that has NextCloud running on it...
I have this share mounted via SMB/CIFS as well there.
I USED to be able to browse and access my files perfectly fine...
However, all of a sudden, navigating to a CHILD dataset, crashes my TrueNAS.
It is a sudden hard crash of the TrueNAS OS for some reason.
Attached 2 screenshots.
You'll notice the process IDs are different, that's just because I had to force this a second time to get the rest of the text.
SOLUTION:
I just made a new Dataset "Windows2" and Child Datasets... transferred all the data from the old Child Datasets to the new Child Datasets... changed the Share location from "Windows" to "Windows2"... set Open ACL again recursively...
And it just worked like it should have originally on Nextcloud. (I did have to run 'sudo -u www-data php occ files:scan --all' in the Nextcloud VM)
The ONLY difference in the setup that I'm aware of right now, is that the old Dataset had a total of 980 snapshots (mostly empty, I actually turned off empty snapshots when I re-enabled them)... So, unless the snapshots existing on the dataset was causing truenas to crash when accessed from Nextcloud, I'm stumped.
ISSUE:
To summarize my setup:
- XCP-ng is installed on the bare server.
- I have 32GB RAM and 8 vCPUs dedicated to TrueNAS (current version 13.0-U3, i updated from U2 seeing if I could fix this issue)
- I have a Dataset "Windows", with 6 Child Datasets "Documents", "Pictures" etc
- - I did this to allow for varied snapshot schedules.
- I have the "Windows" dataset shared via SMB, with open ACL, set recursively to all children.
I can access this share and all children PERFECTLY on my Windows 11 Desktop. Read, Write, whole 9 yards, no problems AT ALL.
However, I have another VM (Ubuntu 20.04) that has NextCloud running on it...
I have this share mounted via SMB/CIFS as well there.
I USED to be able to browse and access my files perfectly fine...
However, all of a sudden, navigating to a CHILD dataset, crashes my TrueNAS.
It is a sudden hard crash of the TrueNAS OS for some reason.
Attached 2 screenshots.
You'll notice the process IDs are different, that's just because I had to force this a second time to get the rest of the text.
SOLUTION:
I just made a new Dataset "Windows2" and Child Datasets... transferred all the data from the old Child Datasets to the new Child Datasets... changed the Share location from "Windows" to "Windows2"... set Open ACL again recursively...
And it just worked like it should have originally on Nextcloud. (I did have to run 'sudo -u www-data php occ files:scan --all' in the Nextcloud VM)
The ONLY difference in the setup that I'm aware of right now, is that the old Dataset had a total of 980 snapshots (mostly empty, I actually turned off empty snapshots when I re-enabled them)... So, unless the snapshots existing on the dataset was causing truenas to crash when accessed from Nextcloud, I'm stumped.
