I am unable to manage permissions from within Windows for one of my shares, the "Samsung_840_Pro" (I get a "invalid parameter" error"). Trying to do so causes samba to:
"NAS kernel: pid 57510 (smbd), uid 0: exited on signal 6 (core dumped)". Also, After a period of time (a few hours?), trying to copy files directly between the "Samsung_840_Pro" share and any other share will cause an empty file with the proper filename to get written to the target of the copy, the copy will stall and fail with a "cannot write; please remove write protection" error, and samba will coredump. Copying from that share to a local PC, then copying the same files to any other share works fine, however. Copying between any shares that are not the "Samsung_840_Pro" works perfectly fine.
"MainVol" is a pool on a set of WD Red drives.
"Samsung_840_Pro" is a separate pool on a single Samsung SSD - the intention was to create a "scratch" drive that I could beat up for temp files, etc. without thrashing the spinning rust. It's an older SSD that works perfectly fine, but is too small to be useful in a laptop.
I've tried re-mapping the shares, and I've tried accessing and remapping the shares on multiple Windows PCs.
Some background:
I have the following pools and volumes:
Here are my CIFS shares:
Here are the datastore permissions options (identical across all of them except for paths):
and the Share settings (identical except for the paths for all my shares, so I'll paste only one):
Here is the permissions view of that Samsung_840_Pro share from a Windows PC (the permissions don't populate):
And here is the same window from the same PC pointing to any other share (note that the permissions are populated):
Trying to apply any permissions settings to the "Samsung_840_Pro" share instantly causes an error, and Samba instantly coredumps with a "code 6". Changing permissions on any other share works fine:
I don't understand what is going on here and how to fix this.
"NAS kernel: pid 57510 (smbd), uid 0: exited on signal 6 (core dumped)". Also, After a period of time (a few hours?), trying to copy files directly between the "Samsung_840_Pro" share and any other share will cause an empty file with the proper filename to get written to the target of the copy, the copy will stall and fail with a "cannot write; please remove write protection" error, and samba will coredump. Copying from that share to a local PC, then copying the same files to any other share works fine, however. Copying between any shares that are not the "Samsung_840_Pro" works perfectly fine.
"MainVol" is a pool on a set of WD Red drives.
"Samsung_840_Pro" is a separate pool on a single Samsung SSD - the intention was to create a "scratch" drive that I could beat up for temp files, etc. without thrashing the spinning rust. It's an older SSD that works perfectly fine, but is too small to be useful in a laptop.
I've tried re-mapping the shares, and I've tried accessing and remapping the shares on multiple Windows PCs.
Some background:
I have the following pools and volumes:
Here are my CIFS shares:
Here are the datastore permissions options (identical across all of them except for paths):
and the Share settings (identical except for the paths for all my shares, so I'll paste only one):
Here is the permissions view of that Samsung_840_Pro share from a Windows PC (the permissions don't populate):
And here is the same window from the same PC pointing to any other share (note that the permissions are populated):
Trying to apply any permissions settings to the "Samsung_840_Pro" share instantly causes an error, and Samba instantly coredumps with a "code 6". Changing permissions on any other share works fine:
I don't understand what is going on here and how to fix this.
