meta data for this page
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| linux:remotefs:nfs [2025/02/26 08:32] – niziak | linux:remotefs:nfs [2025/02/26 08:43] (current) – niziak | ||
|---|---|---|---|
| Line 9: | Line 9: | ||
| on lossy networks. In addition, TCP will handle network speed differences better than UDP, due to the underlying | on lossy networks. In addition, TCP will handle network speed differences better than UDP, due to the underlying | ||
| flow control at the network level. | flow control at the network level. | ||
| + | |||
| + | ===== performance ===== | ||
| + | |||
| + | On server ''/ | ||
| + | * **no_subtree_check** - If a subdirectory of a filesystem is exported, but the whole filesystem isn't then whenever a NFS request arrives, the server must check not only that the accessed file is in the appropriate filesystem (which is easy) but also that it is in the exported tree (which is harder). This check is called the subtree_check. | ||
| + | * **async** - This option allows the NFS server to violate the NFS protocol and reply to requests before any changes made by that request have been committed to stable storage (e.g. disc drive). | ||
| + | * **all_squash** - Map all uids and gids to the anonymous user. Useful for NFS-exported public FTP directories, | ||
| + | |||
| + | On client ''/ | ||
| + | * '' | ||
| + | |||
| ===== diagnostic ===== | ===== diagnostic ===== | ||