October 7, 20169 yr I have a small setup with: Parity: WD Red 3TB Data disk1: WD Red 3TB Data disk2: WD Red 3TB I recently changed the role of a WD Green 500GB from a data drive (previously data Disk2) to a cache drive, mainly for docker apps so that my parity doesn't keep spinning 24/7. Looks like after "tools->new config" my data is still there intact. Former Disk3 is now Disk2. Parity is now rebuilding and much faster than before since I guess the slow WD Green was removed. In the future I will replace it with an SSD. User Shares are: Backup (for Crashplan) appdata (for Docker apps, now on the new cache drive only) nid (personal data) mary (personal data) nid and mary contents are split over disk1 and disk2 (high-water), as have always been. I attach a screenshot of "ls" in the terminal. A) Why Disk2 now has different ownership and permissions? Should I correct this somehow or leave it be? B) Why Disk2 is highlighted green? What does this color code mean anyway? C) What is the "/mnt/user" directory for? It has always been there BUT now a new "user0" directory just appeared. You can see the difference in contents on the screenshot. Is it of any concern? Thanks!
October 7, 20169 yr A) Why Disk2 now has different ownership and permissions? Should I correct this somehow or leave it be? nobody:user is the correct permissions. B) Why Disk2 is highlighted green? What does this color code mean anyway? Here's an explanation at askubuntu. C) What is the "/mnt/user" directory for? It has always been there BUT now a new "user0" directory just appeared. You can see the difference in contents on the screenshot. Is it of any concern? /mnt/user/ = /mnt/disk$/ + /mnt/cache/ /mnt/user0/ = /mnt/disk$/ (Without cache) where $ = disk numbers In summary is looks like at some point disk1 & cache had their ownership changed to root:root and disk2 is the default, all my disks are owned by nobody:users Here's my output: drwxrwxrwx 7 nobody users 4096 Oct 7 12:25 cache/ drwxrwxrwx 3 nobody users 27 Oct 7 11:49 disk1/ drwxrwxrwx 3 nobody users 27 Oct 7 11:49 disk2/ drwxrwxrwx 3 nobody users 15 Oct 7 11:49 disk3/ drwxrwxrwx 3 nobody users 15 Oct 7 11:49 disk4/ drwxrwxrwx 3 nobody users 15 Oct 7 11:49 disk5/ drwxrwxrwx 3 nobody users 15 Oct 7 11:49 disk6/ drwxrwxrwx 3 nobody users 15 Oct 7 11:49 disk7/ drwxrwxrwx 9 nobody users 129 Oct 7 11:49 disk8/ drwxrwxrwx 5 nobody users 62 Oct 7 11:49 disk9/ drwxrwxrwx 2 nobody users 40 Oct 7 11:49 disks/ drwxrwxrwx 1 nobody users 4096 Oct 7 12:25 user/ drwxrwxrwx 1 nobody users 27 Oct 7 11:49 user0/
October 7, 20169 yr Author Don't have a clue how Disk1 and Cache ownership changed but their contents (the user shares) all have nobody:users ownership which I guess is the norm? So should I change the ownership of Disk1 and Cache directories to nobody:users? What would be the command to do that (safely) or is there a way to do it from the WebGui? Should I wait for the parity check first to finish or it's irrelevant? ps. Also user and user0 because they are also root:root right now.
October 7, 20169 yr Community Expert Everything in my /mnt is owned by root except for /mnt/disks created by Unassigned Devices. Never noticed any problems. Maybe this is related to whether or not you use disk shares. I don't.
October 7, 20169 yr Author Everything in my /mnt is owned by root except for /mnt/disks created by Unassigned Devices. Never noticed any problems. Maybe this is related to whether or not you use disk shares. I don't. And what of the ownership of the user shares? They are also owned by root or by nobody? Does it really matter for the operation of the array after all? I just don't want to run into "unexpected" issues in the future, perhaps some docker App will misbehave or whatever, that's why I'm trying to find out what are the "defaults" with the ownership. I don't have any disk shares either.
October 7, 20169 yr The difference in ownership is probably because the one disk is emulated and has been mounted differently. Ownership doesnt particularly matter as long as the permissions associated with it are correct with regards to how unraid utilizes users Sent from my LG-D852 using Tapatalk
October 7, 20169 yr Author The difference in ownership is probably because the one disk is emulated and has been mounted differently. Ownership doesnt particularly matter as long as the permissions associated with it are correct with regards to how unraid utilizes users Sent from my LG-D852 using Tapatalk I don't know what an emulated disk is but I don't see any difference between my disks. So what should I do, change the ownerships or just let it be some root:root and some nobody:users? Thanks
October 7, 20169 yr Community Expert I don't think he has an emulated disk. If I understand correctly, disk 2 was made empty intentionally so it could be moved to the cache slot, then disk3 was move into slot2 with a new config and now parity is rebuilding. nid, Are you sharing disk2?
October 7, 20169 yr I don't think he has an emulated disk. If I understand correctly, disk 2 was made empty intentionally so it could be moved to the cache slot, then disk3 was move into slot2 with a new config and now parity is rebuilding. nid, Are you sharing disk2? Your right. I just saw the red x and didn't look further Sent from my LG-D852 using Tapatalk
October 7, 20169 yr Author I don't think he has an emulated disk. If I understand correctly, disk 2 was made empty intentionally so it could be moved to the cache slot, then disk3 was move into slot2 with a new config and now parity is rebuilding. nid, Are you sharing disk2? Exactly that's what I did. No, I don't have any disk shares at all.
October 7, 20169 yr Community Expert I don't think he has an emulated disk. If I understand correctly, disk 2 was made empty intentionally so it could be moved to the cache slot, then disk3 was move into slot2 with a new config and now parity is rebuilding. nid, Are you sharing disk2? Exactly that's what I did. No, I don't have any disk shares at all. Is disk2 excluded in Global Share Settings?
October 7, 20169 yr Author Is disk2 excluded in Global Share Settings? Never messed with that setting but have a look at the attached screenshot.
October 7, 20169 yr Community Expert That looks right. I would say don't mess with it if it isn't broken in some way. After the parity build completes, reboot, do a non-correcting parity check, and check your disk owners again.
October 8, 20169 yr Author That looks right. I would say don't mess with it if it isn't broken in some way. After the parity build completes, reboot, do a non-correcting parity check, and check your disk owners again. Did exactly these steps. No change in ownerships.
October 8, 20169 yr Another vote here for not messing with it unless you notice any problems. Sent from my LG-H815 using Tapatalk
October 8, 20169 yr Author Could someone explain the difference of the root:root vs nobody:users ownership in this specific scenario (unraid engine, ownerships of various directories under /mnt)? Perhaps then we can understand if it's important or not. I found some info on the nobody user here: http://unix.stackexchange.com/questions/186568/what-is-nobody-user-and-group but I lack the knowledge to put all the pieces together.
October 8, 20169 yr For just about anything ownership doesn't matter it's the permissions that matter. What are the permission differences http://permissions-calculator.org Sent from my LG-D852 using Tapatalk
Archived
This topic is now archived and is closed to further replies.