2024-04-26, 05:01 PM
(This post was last modified: 2024-04-26, 05:01 PM by bitmap. Edited 1 time in total.)
"Mounted" does not mean literally mounted to the hardware. It can be a software mount (i.e., NFS or Samba as @pixel24 states). Depending on your OS(s) this is fairly straightforward. Linux is where I live, so that's what I can describe. Decide on where things will be mounted on the host (housing the drives), decide where everything is mounted on the client (consuming data from the host), install the proper software (nfs-common, nfs-kernel-server), configure the exports on the host (/etc/exports), configure the NFS mounts on the client (/etc/fstab). Last step is to mount the drives on the client (mount -a should work, will require sudo).
Permissions, mount locations, whether to squash access, options like sync and subtree check are the more difficult part. Here's an example of exports and fstab. Access is squashed to the user on the host that has general permissions to all files concerned (GID=998, UID=1000).
Permissions, mount locations, whether to squash access, options like sync and subtree check are the more difficult part. Here's an example of exports and fstab. Access is squashed to the user on the host that has general permissions to all files concerned (GID=998, UID=1000).
Code:
# /etc/exports: the access control list for filesystems which may be exported
# to NFS clients. See exports(5).
#
# Example for NFSv2 and NFSv3:
# /srv/homes hostname1(rw,sync,no_subtree_check) hostname2(ro,sync,no_subtree_check)
#
# Example for NFSv4:
# /srv/nfs4 gss/krb5i(rw,sync,fsid=0,crossmnt,no_subtree_check)
# /srv/nfs4/homes gss/krb5i(rw,sync,no_subtree_check)
#
/mnt/media/core 192.168.x.y(rw,sync,no_subtree_check,anonuid=1000,anongid=998)
/mnt/media/extra 192.168.x.y(rw,sync,no_subtree_check,anonuid=1000,anongid=998)
/mnt/media/multi 192.168.x.y(rw,sync,no_subtree_check,anonuid=1000,anongid=998)
/mnt/backup/multi 192.168.x.y(rw,sync,no_subtree_check,anonuid=1000,anongid=998)
/mnt/backup/tv-flux 192.168.x.y(rw,sync,no_subtree_check,anonuid=1000,anongid=998)
Code:
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda2 during curtin installation
UUID=abc-def-ghi-jkl-mnop / ext4 defaults 0 1
/swap.img none swap sw 0 0
/dev/disk/by-uuid/qrs-tuv-wxy-zab-cdef /mnt/media/core ext4 defaults 0 0
/dev/disk/by-uuid/ghi-jkl-mno-pqr-stuv /mnt/media/extra ext4 defaults 0 0
/dev/disk/by-uuid/wxy-zab-cde-fgh-ijkl /mnt/media/multi ext4 defaults 0 0
/dev/disk/by-uuid/mno-pqr-stu-vwx-yzab /mnt/backup/multi ext4 defaults 0 0
/dev/disk/by-uuid/cde-fgh-ijk-lmn-opqr /mnt/backup/tv-flux ext4 defaults 0 0
192.168.x.y:/mnt/media/flux /mnt/media/flux nfs defaults 0 0
192.168.x.y:/mnt/media/4K /mnt/media/4K nfs defaults 0 0
192.168.x.y:/mnt/backup/critical /mnt/backup/critical nfs defaults 0 0
Jellyfin 10.10.0 LSIO Docker | Ubuntu 24.04 LTS | i7-13700K | Arc A380 6 GB | 64 GB RAM | 79 TB Storage