Jump to content

Am I supposed to have a /user and /user0 directory


danith

Recommended Posts

I always thought it was weird to have both and finally decided to just check

 

root@Dave-San:/mnt# ls
cache/  disk1/  disk2/  disk3/  user/  user0/
root@Dave-San:/mnt# ls -al
total 0
drwxr-xr-x  8 root   root  160 Apr 14 19:51 ./
drwxrwxrwx 19 root   root  400 Sep 28  2012 ../
drwxrwxrwx  4 nobody users  80 Apr 16 04:00 cache/
drwxrwxrwx 13 nobody users 304 Feb 26 22:34 disk1/
drwxrwxrwx 13 nobody users 304 Jun 24  2014 disk2/
drwxrwxrwx  3 nobody users  19 Apr 16 04:00 disk3/
drwxrwxrwx  1 nobody users  80 Apr 16 04:00 user/
drwxrwxrwx  1 nobody users 304 Apr 16 04:00 user0/
root@Dave-San:/mnt# mount -l
tmpfs on /var/log type tmpfs (rw,size=128m,mode=0755)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
/dev/sda1 on /boot type vfat (rw,noatime,nodiratime,umask=0,shortname=mixed) [uNRAID]
nfsd on /proc/fs/nfs type nfsd (rw)
nfsd on /proc/fs/nfsd type nfsd (rw)
/dev/md1 on /mnt/disk1 type reiserfs (rw,noatime,nodiratime,user_xattr,acl)
/dev/md2 on /mnt/disk2 type reiserfs (rw,noatime,nodiratime,user_xattr,acl)
/dev/md3 on /mnt/disk3 type xfs (rw,noatime,nodiratime)
/dev/sdb1 on /mnt/cache type reiserfs (rw,noatime,nodiratime,user_xattr,acl)
shfs on /mnt/user0 type fuse.shfs (rw,nosuid,nodev,noatime,allow_other)
shfs on /mnt/user type fuse.shfs (rw,nosuid,nodev,noatime,allow_other)
/mnt/disk1/docker/containers/docker on /var/lib/docker type btrfs (rw)
root@Dave-San:/mnt# ls user0
Books/  Downloads/  Media/  Music/  TV/  backup/  docker/  movies/  vm_iso/  vm_store/
root@Dave-San:/mnt# ls user
Books/  Downloads/  Media/  Music/  TV/  backup/  docker/  movies/  vm_iso/  vm_store/
root@Dave-San:/mnt#

 

If user and user0 are both valid, what is the purpose of them as they seem to have the same directories

Link to comment

I always thought it was weird to have both and finally decided to just check

 

If user and user0 are both valid, what is the purpose of them as they seem to have the same directories

 

Squid gave you a good answer but to expand a bit.

 

User shares in general aggragate folders from multiple disks.

 

For example, you have a share called Downloads (I am going to assume this isn't cache only even though it likely is...)

 

#What the user share downloads is located at 
/mnt/user/Downloads

#What this user share is actually doing is aggragating the following places into one view
/mnt/disk1/Downloads 
/mnt/disk2/Downloads 
... 
/mnt/diskX/Downloads  
#(Where X is the number of disks in your array that this user share is allowed to be on)
/mnt/cache/Downloads

 

 

This allows you to browse one folder and get a combined view, even though your data is actually in a lot of different folders on different disks.

 

Now for User0

 

#What the user share downloads is located at 
/mnt/user0/Downloads

#What this user share is actually doing is aggragating the following places into one view
/mnt/disk1/Downloads 
/mnt/disk2/Downloads 
... 
/mnt/diskX/Downloads  
#(Where X is the number of disks in your array that this user share is allowed to be on)
# Key difference is that user0 does not include /mnt/cache/Downloads

 

So when you look at the directories under /mnt/user/ and /mnt/user0 they should look exactly the same (maybe not if there are cache only shares... not sure.)

 

Why was explained by Squid already, it's used by the Mover script to help move files on the Cache to a disk in the array.

 

But you can also use user0 if you have a share that uses the cache drive but you want to bypass writing to the cache drive and write directly to the array for some reason. (Or at least I think you can do that, pretty sure it works that way)

 

 

 

 

 

Link to comment

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...