NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

SCUBAInstructor's avatar
Feb 27, 2020
Solved

ReadyNas btrfs subvol

Hi

 

I would like to create a folder next to this one:

/dev/md127 on /apps type btrfs (rw,noatime,nodiratime,nospace_cache,subvolid=259,subvol=/.apps)

 

I can create it like this on the volume:

btrfs subvolume create .runtimes

How to I presistently map it like the /apps above?

 

Best Regards

Jochen

  • You are right, the mount is not permanent.

     

    I have added the below to /etc/fstab:

    UUID=subvolUUID /runtimes btrfs  defaults,subvolid=myID 1 1

    My folder is properly mounted on boot.

     

    Confusing Netgear support is not really my concern. I understand that Netgear only wants to support standard systems.

     

    My device was initially a RDD516 (16 GB RAM). I have changed the DMI (amidedos) so it identifies itself as RN516 and installed ReadyNAS. I have upgraded the CPU to i7-3770K 3.5GHz and installed a X540-T2 10Gigabit 10GBe 10Gbit Dual Port network card. I am running Glassfish, mysql, java11 and some other things to unleash the full potential of that box. Next step is to change disks step by step (higher capacity).

     

    Moving things to /apps folder is a good alternative though.

6 Replies

Replies have been turned off for this discussion
  • Sandshark's avatar
    Sandshark
    Sensei - Experienced User

    The answer is to put an entry into fstab, but why do you want to create an invisible subvolume and then map it to something visible instead of just creating a standard share?  You would have no access to it in the GUI.  Standard shares are already subvolumes, and you can control access via the GUI.

     

    You may also be able to create a .mount file and put it in /etc/systemd/system/multi-user.target.wants, like apps.mount that already resides there, but I have no experience with that.

    • StephenB's avatar
      StephenB
      Guru - Experienced User

      Sandshark wrote:

       just creating a standard share? 


      Definitely better, and you can also set the share to be a hidden share in the Web UI (though it won't start with a .).

    • SCUBAInstructor's avatar
      SCUBAInstructor
      Guide

      Basically I would like to replicate .apps which holds the installed applications on the NAS and is there per default (ReadyNAS).

      I manually installed application on that NAS (mysql) and they should not reside on the root partition (80% usage warning).

       

      My consideration is that if ReadyNAS uses this approach for installed applications (via GUI), it should not be wrong to do the same for my own installations. Is there any problem with this setup?

       

      I found a solution which gives me the exact same result for my folder:

      btrfs subvolume create .runtimes
      mount /dev/md127 -o subvol=.runtimes /runtimes

       

       

      • StephenB's avatar
        StephenB
        Guru - Experienced User

        SCUBAInstructor wrote:

        I found a solution which gives me the exact same result for my folder:

        btrfs subvolume create .runtimes
        mount /dev/md127 -o subvol=.runtimes /runtimes

         


        Your mount command will be need to be manually re-applied every time you reboot the NAS.  There is also some risk down the road that the NAS application (or Netgear Support) will get confused because of the manually created subvolume.  Netgear assumes that its application is the only one that is creating subvolumes on the data volume.

         

        Another approach (easier and commonly used by folks here) is to first install your application(s) in the root as usual.  Then move the folder(s) to the existing /data/.apps subvolume, and create soft link(s) from the root to the new location(s). 

         

        If you want to proceed with a separate subvolume, then IMO a better way is to first create a share called runtimes on the data volume (which can be hidden). Then create a soft link to that subvolume in the root.

        # ln -s /data/runtimes /runtimes

        That avoids the need for a persistent mount.  It also allows you manage snapshots for /data/runtimes, back it up, etc using the built in tools in the ReadyNAS GUI.

NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology! 

Join Us!

ProSupport for Business

Comprehensive support plans for maximum network uptime and business peace of mind.

 

Learn More