What are some best practices in mounting NAS shares that you all follow?

Currently I am mounting using fstab to my user’s home directory with full rwx permissions, but that feels wrong.

I’ve read to use the mnt directory or the media directory but opinions differ.

My main concern is I want to protect against inadvertently deleting the contents of the NAS with an errant rm command. And yes I have backups of my NAS too.

Edit: this is a home NAS with 1 user on this Linux PC (the other clients being windows and Mac systems)

Would love to hear everyone’s philosophy! Thanks!

  • UntouchedWagons@lemmy.caEnglish
    0·
    2 years ago

    I use systemd mount files instead of fstab, that way I can specify a network dependency in the off chance there’s no network connection. Plus I can have other services like jellyfin depend on that mount file so it starts after the share is available.

    • steel_moose@lemmy.world
      1·
      2 years ago

      Dipping my toes into this as well. Would you care to share the contents of your .mount unit file?

      If I understand it correctly systemd generates unit files at boot using fstab 🤔. Probably not possible to specify the network dependency in fstab.

      • UntouchedWagons@lemmy.caEnglish
        2·
        2 years ago
        #cat /etc/systemd/system/mnt-data.mount
[Unit]
Description=nfs mount script

[Mount]
What=192.168.0.30:/mnt/tank/Media
Where=/mnt/data
Type=nfs4

[Install]
WantedBy=remote-fs.target

        The file name has to match the folder upon which the share is mounted with hypens instead of forward slashes

    • Rockslide0482@discuss.tchncs.deEnglish
      0·
      2 years ago

      in fstab, there’s a nofail option that I started using when mounting NFS and other disks that may be missing and I don’t want to kill my bootup

  • 0x4E4F@infosec.pubEnglish
    0·
    2 years ago

    Mounting it in fstab is a bad idea… in home even worse.

    Just make some desktop entries with the shares and that should be enough.

      • 0x4E4F@infosec.pubEnglish
        0·
        2 years ago

        Well, for one, it’s network attached storage. If it’s not present in the network for one reason or another, guess what, your OS doesn’t boot… or it errors during boot, depending on how the kernel was compiled and what switches your bootloader sends to the kernel during boot. Second, this is an easy way for malware to spread, especially if it’s set to run after user logon.

        • Scholars_Mate@lemmy.worldEnglish
          0·
          2 years ago

          Well, for one, it’s network attached storage. If it’s not present in the network for one reason or another, guess what, your OS doesn’t boot… or it errors during boot, depending on how the kernel was compiled and what switches your bootloader sends to the kernel during boot.

          Just use nofail in the fstab.

          Second, this is an easy way for malware to spread, especially if it’s set to run after user logon.

          If your fileshare is accessible to you, it is also accessible to malware running as your user. Mounting the share via a filemanager doesn’t change this.