nzbget 21.1 stable on os 6.10.7

ok this is new to me.  

The ReadyNAS apps folder is a mount point to the data volume (/data/.apps in a ReadyNAS using XRAID).

when i ssh in and drill down to the root and do an 'ls' it shows the usual folders (bin, etc, home, yadda yadda), plus the two volumes that i have my drives set up as (Vol1 and Vol2), plus the 'Apps' directory, where the default packages available to me would be installed had i gone through the default package manager.

you're saying that the apps folder is really just a shortcut to a folder in the data directory?  sorry, this is the first time i'm being told theres such a thing called a 'mount point'. 

thanks for chiming in! 

Can you do a ls -l in the apps directory? is nzbget list, if so do the same in it's folder.

What do you see?

---

b1jzcbx wrote:

 

you're saying that the apps folder is really just a shortcut to a folder in the data directory?  sorry, this is the first time i'm being told theres such a thing called a 'mount point'. 

 

---

If you run mount, you can see this.  There are a lot of mounts on the ReadyNAS, so I used grep to only show the one of interest.

root@NAS:~# mount | grep -i app
/dev/md127 on /apps type btrfs (rw,noatime,nodiratime,nospace_cache,subvolid=258,subvol=/.apps)
root@NAS:~#

md127 is the RAID array (think of it as a virtual disk) for my data volume. So /data/.apps is being mounted on /apps.

This isn't quite the same as a shortcut.  There is an empty placeholder folder called /apps in the OS partition.  That empty placeholder is the "mount point".  The OS mounts /data/.apps "over" that folder as part of the boot process.

There is a brief sketch of the concept here: https://opensource.com/life/16/10/introduction-linux-filesystems (scroll down to the "Mounting section). 

Filesystems are mounted on an existing directory/mount point using the mount command. In general, any directory that is used as a mount point should be empty and not have any other files contained in it. Linux will not prevent users from mounting one filesystem over one that is already there or on a directory that contains files. If you mount a filesystem on an existing directory or filesystem, the original contents will be hidden and only the content of the newly mounted filesystem will be visible.

Note you can remount the OS to /mnt using this command:

# mount --bind / /mnt

When you do this, exploring /mnt lets you examine the root file system without the mounts getting in the way. So if you enter ls -l /mnt/apps, you will see it is empty.

root@NAS:~# ls -als /mnt/apps
total 16
 0 drwxrwxr-x 1 admin admin   0 Mar  7  2017 .
16 drwxr-xr-x 1 root  root  260 Apr  7 00:05 ..
root@NAS:~#

BTW, if you do try this, you undo it by

# cd //
# umount /mnt

The umount will fail if you are inside /mnt - the cd // ensures that is not the case. 

well I'm VERY glad you pointed the facets of the apps folder out to me.  thank you!  saves me a whole lotta headache!

so i guess i'll just leave it as is.  when i set up the nas, i did everything as root, including the letsencrypt update from rnxtras.  then i created my 2 volumes.  the last thing i did was create additional user accounts.  basically, i get it all running and updated first before installing additional software and users.

thanks!