Traditional file systems could exist on a single disk alone at a time. The file system is now aware of the underlying structure of the disks. More than a file system, ZFS is fundamentally different from traditional file systems.Ĭombining the traditionally separate roles of volume manager and file system provides ZFS with unique advantages. Common Address Redundancy Protocol (CARP) File and Print Services for Microsoft® Windows® Clients (Samba) Dynamic Host Configuration Protocol (DHCP) Lightweight Directory Access Protocol (LDAP) Locale Configuration for Specific Languages FreeBSD as a Guest on VMware Fusion for macOS® FreeBSD as a Guest on Parallels Desktop for macOS® RAID3 - Byte-level Striping with Dedicated Parity GEOM: Modular Disk Transformation Framework Debian / Ubuntu Base System with debootstrap(8) Installing Applications: Packages and Ports Accounts, Time Zone, Services and Hardening If you need to share to multiple subnets, you would do something like: sudo zfs set \įor more information about the available parameters, refer to the section called "New ZFS Sharing Syntax" in Oracle-s documentation: Sharing and Unsharing ZFS File Systems. Share="name=my-share,path=/path/on/server,prot=nfs,sec=sys,rw=*,public" \ You can chain any number of parameters separated by commas. You can use the command below to give read/write access to all hosts on the 192.168.11.0/24 subnet (e.g. For this, we would use a more sophisticated command on the host. You probably only want to give one specific host, or a specific group of hosts, access. In a lot of situations, you would not be happy to give every host on your network access to your NFS. This scenario would give NFS access to any host on your network that can access. or in the case of an addition to your /etc/fstab file for auto-mounting on boot: :/pool-name/dataset-name /path/to/local/mount nfs auto 0 0 This could be with the command: mount -t nfs \ If you didn't create a dataset, and just have the pool, you can still do: zfs set sharenfs=on pool-name Sharing a dataset can be as easy as: zfs set sharenfs=on pool-name/dataset-name sudo apt-get install -y nfs-kernel-server Stepsįirstly, install the nfs-kerenel-server service if you haven't already. If you don't set up that child for sharing, the client will see the dataset folder, but not be able to access it. This is great from a security point-of-view, but I realize it can be a bit annoying. For example, if you have a dataset that is the parent of another, you would still have to set up sharing on that child if you wanted it to be shared, even if you have already set up sharing on the parent. Each dataset is treated like its own filesystem, with its own rules and settings, which means with regards to sharing over NFS, that you can share more securely as client's will not be able to reach out of the bounds of that dataset/filesystem that you decided to share.Īn important thing to bear in mind is that you will need to run the steps below for sharing on every pool/dataset that you wish to share, no matter the hierarchy. The great thing about ZFS is that it is very easy to split your "pool" into as many datasets as you like. It is important to use one or the other for sharing your ZFS datasets, but never both. This is because we will be using ZFS to manage the ZFS shares, and not /etc/exports. When it comes to sharing ZFS datasets over NFS, I suggest you use this tutorial as a replacement to the server-side tutorial. You might have seen my previous tutorials on setting up an NFS server and a client.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |