Unlisted Person
Cadet
- Joined
- Mar 15, 2016
- Messages
- 6
I have an existing NFS server that I'm replacing with a FreeNAS system. The existing setup is that the NFS server has individual backup directories per IP-based server where each server gets access
only to it's own share/sub-directory.
So the existing physical setup on the old server is something like
With access to each share being managed by IP address. In ext4 with NFS4 you'd setup an exports file like this:
I also have a parent NFS share that can be accessed and see all the subdirectories for the individual servers as read only: e.g. adding this to the exports file
So I'd like to setup something similar in FreeNAS, but while setting up the first NFS share was fine for the first share (server1), with the next share (server2) where I try to limit by IP I get
I don't understand why there's this limitation for shares via NFS under FreeNAS, but ok, fine if there's a workaround.
In looking at the documentation and forums it appears the that the of discussion suggests either creating jails, datasets, or using CIFS instead.
I know CIFS is not the best tool for this implementation as this is a server connection with access by IP, not shared by user perms, and this without any MS Windows stuff.
It appears that jails are for when you want to run some software from a share - so I think I don't need that.
I think a ZFS Dataset is simply a mountpoint folder which allows for additional features such as permissions for files and folders contained within that mountpoint. There won't be file transfer between datasets (I understand there's a performance hit on moving files between datasets on the same disk because ZFS treats different datasets as separate file systems). So ZFS datasets seems to be the best fit for what I want to do?
I wanted to know what the best practices were in regards to setting up a ZFS dataset correctly for this setup:
This thread talking about child datasets, but I don't see anything in the docs that discusses child datasets.
So the top question I have is what's the best practice here?
I'm guessing something like this:
* Do I have to create N+1 datasets where N is the number of servers, and the extra one is for the read-only share?
* If I share a parent dataset do all child datasets also appear even if child datasets are shared only to a specific IP address?
* Should (Can) I specify where datasets appear and use where the directories are already there? Or is it that (it appears in FreeNAS) all datasets created in /mnt (and below for child datasets)?
only to it's own share/sub-directory.
So the existing physical setup on the old server is something like
Code:
/path/to/share/server1 /path/to/share/server2 /path/to/share/server3 (etc)
With access to each share being managed by IP address. In ext4 with NFS4 you'd setup an exports file like this:
Code:
/path/to/share/server1 x.x.x.1(rw,..... /path/to/share/server2 x.x.x.2(rw,.... /path/to/share/server3 x.x.x.3(rw,.... etc.
I also have a parent NFS share that can be accessed and see all the subdirectories for the individual servers as read only: e.g. adding this to the exports file
Code:
/path/to/share/ x.x.x.y(ro,....)
So I'd like to setup something similar in FreeNAS, but while setting up the first NFS share was fine for the first share (server1), with the next share (server2) where I try to limit by IP I get
"The network 0.0.0.0/0 is already being shared and cannot be used twice for the same filesystem"I don't understand why there's this limitation for shares via NFS under FreeNAS, but ok, fine if there's a workaround.
In looking at the documentation and forums it appears the that the of discussion suggests either creating jails, datasets, or using CIFS instead.
I know CIFS is not the best tool for this implementation as this is a server connection with access by IP, not shared by user perms, and this without any MS Windows stuff.
It appears that jails are for when you want to run some software from a share - so I think I don't need that.
I think a ZFS Dataset is simply a mountpoint folder which allows for additional features such as permissions for files and folders contained within that mountpoint. There won't be file transfer between datasets (I understand there's a performance hit on moving files between datasets on the same disk because ZFS treats different datasets as separate file systems). So ZFS datasets seems to be the best fit for what I want to do?
I wanted to know what the best practices were in regards to setting up a ZFS dataset correctly for this setup:
This thread talking about child datasets, but I don't see anything in the docs that discusses child datasets.
So the top question I have is what's the best practice here?
I'm guessing something like this:
* Do I have to create N+1 datasets where N is the number of servers, and the extra one is for the read-only share?
* If I share a parent dataset do all child datasets also appear even if child datasets are shared only to a specific IP address?
* Should (Can) I specify where datasets appear and use where the directories are already there? Or is it that (it appears in FreeNAS) all datasets created in /mnt (and below for child datasets)?
