From 8989a098b20d784aa0064ba8eeadb86bd9dae1df Mon Sep 17 00:00:00 2001 From: robbyandrews <33102078+robbyandrews@users.noreply.github.com> Date: Mon, 18 Mar 2024 21:32:48 -0700 Subject: [PATCH 1/2] update NFS being available only in global zone. --- docs/configuring-nfs-in-smartos.md | 4 +--- docs/is-smartos-suitable-for-a-file-server.md | 23 ------------------- 2 files changed, 1 insertion(+), 26 deletions(-) diff --git a/docs/configuring-nfs-in-smartos.md b/docs/configuring-nfs-in-smartos.md index 18a46e1..4795eba 100644 --- a/docs/configuring-nfs-in-smartos.md +++ b/docs/configuring-nfs-in-smartos.md @@ -3,9 +3,7 @@ NFS (network file system) provides access to remote filesystems which -appear similar to local resources on client hosts. Currently on -SmartOS, NFS can only be served from the **global zone**. It is highly -recomended to use [SMB](configuring-smb-in-smartos.md) in zones instead. +appear similar to local resources on client hosts. The following focuses on NFS server and client configurations in SmartOS. Our host details are: diff --git a/docs/is-smartos-suitable-for-a-file-server.md b/docs/is-smartos-suitable-for-a-file-server.md index 8695abb..d51055c 100644 --- a/docs/is-smartos-suitable-for-a-file-server.md +++ b/docs/is-smartos-suitable-for-a-file-server.md @@ -14,29 +14,6 @@ There are two features of SmartOS that make it attractive for a NAS: ever be corrupted. If it is, just re-flash it, and you are off and running again. -But there are a couple of issues that make implementing a NAS -problematic. - -First, NFS is available only in the global zone (GZ). It seems this will -be fixed someday. But for now it means we can only NFS share filesystems -out of the GZ. The NFS share information is stored in the ZFS datasets, -so the persistence issue doesn't bite us here. If all you need is NFS -file sharing, SmartOS is an excellent solution. But most people need to -support Windows and/or Apple clients. - -Second, the transient nature of the GZ. It is possible to install -packages (such as Samba or Netatalk) in the GZ and work around the -persistence issue, but this contradicts the design and intention of -SmartOS and it is not recommended. The SmartOS way is to keep the GZ -pristine and light -- just ZFS and management of virtual machines -- and -do everything else in the VMs. - -For these reasons, someone looking for a straight NAS is probably better -served using another platform, such as OmniOS, perhaps using Napp-it to -simplify management. - -But if you also need virtualization, SmartOS starts to become much more -attractive, and it may be worthwhile to workaround the above problems. Here are some approaches that have been used successfully: From a222ada4b2b6b234125e3f43b39f1fa6abadaf4b Mon Sep 17 00:00:00 2001 From: robbyandrews <33102078+robbyandrews@users.noreply.github.com> Date: Tue, 19 Mar 2024 10:15:17 -0700 Subject: [PATCH 2/2] fix extra blank lines --- docs/is-smartos-suitable-for-a-file-server.md | 1 - 1 file changed, 1 deletion(-) diff --git a/docs/is-smartos-suitable-for-a-file-server.md b/docs/is-smartos-suitable-for-a-file-server.md index d51055c..ac0f0e8 100644 --- a/docs/is-smartos-suitable-for-a-file-server.md +++ b/docs/is-smartos-suitable-for-a-file-server.md @@ -14,7 +14,6 @@ There are two features of SmartOS that make it attractive for a NAS: ever be corrupted. If it is, just re-flash it, and you are off and running again. - Here are some approaches that have been used successfully: 1. Create a zone. To support Windows and Mac clients either run CIFS or