eduardooliveira
Dabbler
- Joined
- Feb 10, 2023
- Messages
- 13
Hi,
We just started to use Truenas Scale coming from previous experience with Truenas Core. This is a brand-new install, not a migration from one system (Core) to the other (Scale).
So, accessing folders from a Windows machine is fine and all permissions are set properly (no one has issues creating files, folders etc) except for one thing...
When making a copy of any existing folder and trying to rename it will say that the folder is already open on another machine or opened by another person when it is not! If we wait a couple of minutes (5 -10 min or so) it will allow us to rename the folder with no problems. Oh, we can rename the original folder with no problems, only the new folder copy cannot be renamed....
That said, this is not a permissions issue but something that is getting stuck right after the copy of the folder is created and preventing it to be renamed.
These folders came from a Windows 10 computer that was acting as a file server before where this issue was NOT happening. It only started after we deployed the Truenas Scale. I have implemented Truenas Core in the same scenario (moving from a Windows Machine action as a file server to Truenas) and that was not a problem at all...
There is nothing unique about the folders really. only a few subfolders, some empty and some with word/excel/PDF files.
Also, we can delete the new folder copy but some subfolders may say that they are open and/or cannot be deleted (even some there were already empty when copied from the template folder). I also investigated hidden contents and there is nothing inside these folders. Again, trying a few minutes later that works ok OR if you do it from another computer (same user or different user, does not matter)
So, the interesting fact is... if I try to rename or delete that new folder that was just duplicated but now from a DIFFERENT machine without waiting (all Windows 10 running the same build) that will work just fine. But not from the machine that created the copy.
Any ideas?
I do not think that this is an issue with the server-side copies failing on the machines since 1) it still works on any other shares, not on the Truenas, 2) I can still rename or delete from another computer the second the copy of the folder is created 3) affects all computers in the network when they create a copy of the folders, 4) there are only 6-7 computers on the network at the same time at maximum (normally 5) and they are not all the time accessing files on the Truenas Shares (or even the same folders at the same time)
We just started to use Truenas Scale coming from previous experience with Truenas Core. This is a brand-new install, not a migration from one system (Core) to the other (Scale).
So, accessing folders from a Windows machine is fine and all permissions are set properly (no one has issues creating files, folders etc) except for one thing...
When making a copy of any existing folder and trying to rename it will say that the folder is already open on another machine or opened by another person when it is not! If we wait a couple of minutes (5 -10 min or so) it will allow us to rename the folder with no problems. Oh, we can rename the original folder with no problems, only the new folder copy cannot be renamed....
That said, this is not a permissions issue but something that is getting stuck right after the copy of the folder is created and preventing it to be renamed.
These folders came from a Windows 10 computer that was acting as a file server before where this issue was NOT happening. It only started after we deployed the Truenas Scale. I have implemented Truenas Core in the same scenario (moving from a Windows Machine action as a file server to Truenas) and that was not a problem at all...
There is nothing unique about the folders really. only a few subfolders, some empty and some with word/excel/PDF files.
Also, we can delete the new folder copy but some subfolders may say that they are open and/or cannot be deleted (even some there were already empty when copied from the template folder). I also investigated hidden contents and there is nothing inside these folders. Again, trying a few minutes later that works ok OR if you do it from another computer (same user or different user, does not matter)
So, the interesting fact is... if I try to rename or delete that new folder that was just duplicated but now from a DIFFERENT machine without waiting (all Windows 10 running the same build) that will work just fine. But not from the machine that created the copy.
Any ideas?
I do not think that this is an issue with the server-side copies failing on the machines since 1) it still works on any other shares, not on the Truenas, 2) I can still rename or delete from another computer the second the copy of the folder is created 3) affects all computers in the network when they create a copy of the folders, 4) there are only 6-7 computers on the network at the same time at maximum (normally 5) and they are not all the time accessing files on the Truenas Shares (or even the same folders at the same time)