This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
admin-nfs [2022/01/18 21:14] – rs232 | admin-nfs [2024/10/21 19:49] (current) – -Condense, formatting hogwild | ||
---|---|---|---|
Line 1: | Line 1: | ||
===== NFS Server ===== | ===== NFS Server ===== | ||
- | The built in NFS server | + | FreshTomato' |
- | {{: | + | It's essentially the equivalent of Samba in a Linux environment. |
- | **Enable NFS Server** | + | |
- | **Enable legacy (NFS V2) support** | + | |
+ | |||
+ | **Enable NFS Server:** sets the NFS server process | ||
+ | |||
+ | \\ | ||
+ | |||
+ | **Enable legacy (NFS V2) support: **enables support for NFS version 2. | ||
+ | |||
+ | NFS currently | ||
+ | |||
+ | \\ | ||
+ | |||
+ | **Exports**\\ {{: | ||
+ | |||
+ | **Directory: | ||
+ | |||
+ | \\ | ||
+ | |||
+ | **IP Address/ | ||
+ | |||
+ | \\ | ||
+ | |||
+ | **Access: ** defines the share permissions (how the share can be accessed). | ||
+ | |||
+ | \\ | ||
+ | |||
+ | * Read-only | ||
+ | * Read/ | ||
+ | |||
+ | \\ | ||
+ | |||
+ | **Sync/ | ||
+ | |||
+ | * Synchronous - FreshTomato will only acknowledge data after it's been written out | ||
+ | |||
+ | * Async(hronous) - FreshTomato will acknowledge data before it's been written out. \\ The NFS server will acknowledge data before it's committed to disk. \\ If the server crashes, this can lead to data corruption. | ||
+ | |||
+ | \\ | ||
+ | |||
+ | **Subtree Check:** | ||
+ | |||
+ | * No * - subtree check will be disabled. | ||
+ | * Yes - enables subtree checking. | ||
+ | |||
+ | \\ | ||
+ | |||
+ | This has minor security implications, | ||
+ | |||
+ | In NFS, if a filesystem subdirectory is exported, but not the whole filesystem, then whenever a NFS request arrives, the server must check the accessed file is in the appropriate filesystem (easy) and that it is in the exported tree (harder). This check is called the subtree_check. | ||
+ | |||
+ | To perform the check, the server must include details of the file location in the file handle given to the client. This can cause problems accessing files that are renamed while a client has them open. However, in many simple cases, it will still work. | ||
+ | |||
+ | \\ | ||
+ | |||
+ | **Other Options: | ||
+ | |||
+ | Please refer to official NFS documentation for details. [[https:// | ||
+ | |||
+ | \\ \\ | ||
- | **Exports**\\ | ||
- | {{: | ||
- | **Directory** - Filesystem location to be shared\\ | ||
- | **IP Address/ | ||
- | **Access** - Defined how the Share can be accessed as in Read-only or Read/ | ||
- | **Sync/ | ||
- | **Subtree_check** - Helps when one folder is exported but one or more of the subfolders is not.\\ | ||
- | **Other_options** - Here you specify advanced options. Please refer to the official NFS documentation for additional details.\\ | ||