-
Important Announcement for the TrueNAS Community.
The TrueNAS Community has now been moved. This forum has become READ-ONLY for historical purposes. Please feel free to join us on the new TrueNAS Community Forums
two owners for one dataset
- Thread starter pet1022
- Start date
- Joined
- Mar 6, 2014
- Messages
- 9,553
Files / directories only have one owner. You are changing owner from paul to peter.
Hello,
Yes, that's what I thought at first.
In the web interface, when I assigned the "TOTO" directory as "main directory" to Peter, Truenas did not throw me out. He should have warned me that this dataset already had an owner.
Or, he de-assigned Paul's "TOTO" to Peter's profile record. But when I went to Paul's profile, "TOTO" was still assigned as Paul's "main directory".
I have not yet gone to see (in command line) who was the real owner of the "TOTO" dataset.
But in the web interface, there should be an "alert", because visually in their respective profiles, peter and paul are both owners of "TOTO".
Yes, that's what I thought at first.
In the web interface, when I assigned the "TOTO" directory as "main directory" to Peter, Truenas did not throw me out. He should have warned me that this dataset already had an owner.
Or, he de-assigned Paul's "TOTO" to Peter's profile record. But when I went to Paul's profile, "TOTO" was still assigned as Paul's "main directory".
I have not yet gone to see (in command line) who was the real owner of the "TOTO" dataset.
But in the web interface, there should be an "alert", because visually in their respective profiles, peter and paul are both owners of "TOTO".
Hello,
I have done some tests.
Indeed, by doing an ls -l on the datasets, the owner has changed. But in the web interface, when you go to their respective profiles, Paul and Peter are both "owner" of the same dataset "TOTO". A restart of the server is not enough to update the right parameters.
Be careful who is the owner, because as in my case, it played tricks for my ssh connection.
To redefine the initial owner (without going through the command line), you have to unlink the two users defined on the same dataset (for example by putting them in /nonexistent), and only then redefine the initial user.
I have done some tests.
Indeed, by doing an ls -l on the datasets, the owner has changed. But in the web interface, when you go to their respective profiles, Paul and Peter are both "owner" of the same dataset "TOTO". A restart of the server is not enough to update the right parameters.
Be careful who is the owner, because as in my case, it played tricks for my ssh connection.
To redefine the initial owner (without going through the command line), you have to unlink the two users defined on the same dataset (for example by putting them in /nonexistent), and only then redefine the initial user.
Hello,
It's not that obvious. In the web interface, and unless I'm mistaken, when you define a personal directory on a user's profile, this user automatically becomes the owner of it!
No, this is not a good idea, but this manipulation could be "forbidden" by Truenas.
In my case I was testing my datasets and I needed to put a user on another dataset, I didn't know if this one already had an owner defined, it's by pure chance that I discovered this. But this could happen in production mode, and we would not be notified that the owner of a dataset has changed.
It's not that obvious. In the web interface, and unless I'm mistaken, when you define a personal directory on a user's profile, this user automatically becomes the owner of it!
No, this is not a good idea, but this manipulation could be "forbidden" by Truenas.
In my case I was testing my datasets and I needed to put a user on another dataset, I didn't know if this one already had an owner defined, it's by pure chance that I discovered this. But this could happen in production mode, and we would not be notified that the owner of a dataset has changed.
