Différences

Ci-dessous, les différences entre deux révisions de la page.

--- tech:draft-nfsv4-sous-debian [2025/10/03 01:17] – Jean-Baptiste
+++ tech:draft-nfsv4-sous-debian [2026/01/12 15:32] (Version actuelle) – Jean-Baptiste
@@ Ligne 14: / Ligne 14: @@
 * http://wiki.linux-nfs.org/wiki/index.php/Nfsv4_configuration
 * https://www.suse.com/communities/blog/configuring-nfsv4-server-and-client-suse-linux-enterprise-server-10/
+* https://blog.stephane-robert.info/docs/services/stockage/nfs/
+* https://inetdoc.net/pdf/sysadm-net.nfs.pdf
@@ Ligne 31: / Ligne 32: @@
 En NFSv4 contrairement aux versions précédentes seul le port TCP 2049 suffit
 == Sur le serveur
@@ Ligne 56: / Ligne 58: @@
 </code>
-<code ini /etc/default/nfs-common>
+''/etc/default/nfs-common''
+<code ini>
 NEED_STATD=no
 STATDOPTS=
@@ Ligne 65: / Ligne 68: @@
 </code>
-<code ini /etc/default/nfs-kernel-server>
+''/etc/default/nfs-kernel-server''
+<code ini>
 # /usr/sbin/rpc.mountd --manage-gids -N 2 -N 3 -V 4 -V 4.1
 # man rpc.mountd
@@ Ligne 73: / Ligne 77: @@
-<code - /etc/exports>
+''/etc/exports''
+<code ->
 # Example for NFSv4:
 # /srv/nfs4        gss/krb5i(rw,sync,fsid=0,crossmnt,no_subtree_check)
 # /srv/nfs4/homes  gss/krb5i(rw,sync,no_subtree_check)
 #
-/export         192.168.1.0/24(rw,sync,fsid=0,no_subtree_check) 127.0.0.1(rw,sync,fsid=0,no_subtree_check)
+/export         192.168.1.0/24(rw,sync,fsid=0,crossmnt,no_subtree_check) 127.0.0.1(rw,sync,fsid=0,crossmnt,no_subtree_check)
 /export/partage 192.168.1.0/24(rw,sync,nohide,insecure,no_subtree_check) 127.0.0.1(rw,sync,nohide,insecure,no_subtree_check)
 </code>
@@ Ligne 99: / Ligne 104: @@
 Notes : pour une base de donnée Postgres sur le serveur il faut absolument mettre l'option ''hard'' et il est recommandé de mettre coté serveur ''sync''
+The only firm requirement for using NFS with PostgreSQL is that the file system is mounted using the hard option. With the hard option, processes can “hang” indefinitely if there are network problems, so this configuration will require a careful monitoring setup. The soft option will interrupt system calls in case of network problems, but PostgreSQL will not repeat system calls interrupted in this way, so any such interruption will result in an I/O error being reported.
+It is not necessary to use the sync mount option. The behavior of the async option is sufficient, since PostgreSQL issues fsync calls at appropriate times to flush the write caches. (This is analogous to how it works on a local file system.) However, it is strongly recommended to use the sync export option on the NFS server on systems where it exists (mainly Linux). Otherwise, an fsync or equivalent on the NFS client is not actually guaranteed to reach permanent storage on the server, which could cause corruption similar to running with the parameter fsync off. The defaults of these mount and export options differ between vendors and versions, so it is recommended to check and perhaps specify them explicitly in any case to avoid any ambiguity.
+Source: https://www.postgresql.org/docs/current/creating-cluster.html
@@ Ligne 122: / Ligne 134: @@
 </code>
-<code ini /etc/default/nfs-common>
+''/etc/default/nfs-common''
+<code ini>
 NEED_STATD=no
 STATDOPTS=
@@ Ligne 130: / Ligne 143: @@
 </code>
-<code - /etc/fstab>
+''/etc/fstab''
+<code ->
 .168.1.10:/partage  /mnt/nfs nfs4    _netdev,noatime,bg,soft,rw,nodev,nosuid,noexec,noauto,proto=tcp,port=2049,vers=4.1,timeo=5,retrans=5,actimeo=10,retry=5  0  0
 </code>
@@ Ligne 162: / Ligne 176: @@
 Voir /var/lib/nfs/
+=== Disable rpcbind on NFS server (RedHat)
+Source : https://www.spinics.net/linux/fedora/fedora-users/msg513100.html
+<code bash>
+systemctl mask --now rpc-statd.service rpcbind.service rpcbind.socket
+systemctl restart nfs-server
+</code>
 === Obtenir des info sur le montage / quelle version de NFS
@@ Ligne 168: / Ligne 193: @@
 nfsstat -m
 </code>
 === Client Autofs
-<code - /etc/auto.master>
+''/etc/auto.master''
+<code ->
 /mnt/nfs        /etc/auto.nfs --ghost,--timeout=60
 </code>
-<code - /etc/auto.nfs>
+''/etc/auto.nfs''
+<code ->
 partage  -fstype=nfs4,noatime,bg,soft,rw,nodev,nosuid,noexec,proto=tcp,port=2049,vers=4.1,timeo=5,retrans=5,actimeo=10,retry=5  192.168.1.10:/partage
 </code>
 === Démonter une partition NFS en erreur
@@ Ligne 184: / Ligne 213: @@
 umount -lf /mnt/nfs
 </code>
 === Liste des partages
@@ Ligne 238: / Ligne 268: @@
 </code>
+== Err nfs-server.service is masked (RedHat)
+<code ->
+# systemctl enable --now nfs-server.service
+Failed to enable unit: Unit file /etc/systemd/system/nfs-server.service is masked.
+# ls -l /etc/systemd/system/nfs-server.service
+lrwxrwxrwx. 1 root root 9 Apr 24  2024 /etc/systemd/system/nfs-server.service -> /dev/null
+# rm /etc/systemd/system/nfs-server.service
+rm: remove symbolic link '/etc/systemd/system/nfs-server.service'? y
+# systemctl enable --now nfs-server.service
+Created symlink /etc/systemd/system/multi-user.target.wants/nfs-server.service → /usr/lib/systemd/system/nfs-server.service.
+Job for nfs-server.service canceled.
+</code>