Reexport NFS directories without the need to restart NFSD
Posted: Mon Sep 23, 2019 4:58 pm
I had a need to add a new subnet to an exported directory on the NFS server. The server has some exported directories and I don't want to restart nfs to potentially affect other currently mounted directories to NFS clients.
The way to do it is to use '"exportfs -arv".
1. Check current exported file systems on laxm1311. 10.0.23.0/24 is not included for /usr/sap/trans (/export/trans)
2. Run exportfs -arv command to add the new subnet (10.0.23.0/24)
3. Check exported file systems on laxm1311 again. New subnet appears.
All without restarting NFSD.
I then mounted /usr/sap/trans on laxm1261 (10.0.23.36) successfully.
The way to do it is to use '"exportfs -arv".
1. Check current exported file systems on laxm1311. 10.0.23.0/24 is not included for /usr/sap/trans (/export/trans)
Code: Select all
laxm1311:/%exportfs
/export/sapmnt 10.0.24.0/24
/export/sapmnt 10.0.26.0/24
/export/trans 10.0.22.0/24
/export/trans 10.0.24.0/24
/export/trans 10.0.26.0/24
/export/oraarch2
10.0.24.0/24
/export/trans_cofiles
10.0.24.0/24
/export/trans_data
10.0.24.0/24
Code: Select all
laxm1311:/%exportfs -arv
exporting 10.0.24.0/24:/export/trans_data
exporting 10.0.24.0/24:/export/trans_cofiles
exporting 10.0.24.0/24:/export/oraarch2
exporting 10.0.22.0/24:/export/trans
exporting 10.0.23.0/24:/export/trans
exporting 10.0.24.0/24:/export/trans
exporting 10.0.26.0/24:/export/trans
exporting 10.0.24.0/24:/export/sapmnt
exporting 10.0.26.0/24:/export/sapmnt
Code: Select all
laxm1311:/%exportfs
/export/sapmnt 10.0.24.0/24
/export/sapmnt 10.0.26.0/24
/export/trans 10.0.22.0/24
/export/trans 10.0.23.0/24
/export/trans 10.0.24.0/24
/export/trans 10.0.26.0/24
/export/oraarch2
10.0.24.0/24
/export/trans_cofiles
10.0.24.0/24
/export/trans_data
10.0.24.0/24
I then mounted /usr/sap/trans on laxm1261 (10.0.23.36) successfully.
Code: Select all
laxm1261:/ %mount -v /usr/sap/trans
mount.nfs4: timeout set for Mon Sep 23 13:39:43 2019
mount.nfs4: trying text-based options 'intr,vers=4.1,addr=10.0.24.50,clientaddr=10.0.23.36'
mount.nfs4: mount(2): Protocol not supported
mount.nfs4: trying text-based options 'intr,vers=4.0,addr=10.0.24.50,clientaddr=10.0.23.36'
laxm1261:/ %df -hP
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/rootvg-LogVol00 59G 8.4G 48G 15% /
devtmpfs 48G 0 48G 0% /dev
tmpfs 48G 492K 48G 1% /dev/shm
tmpfs 48G 70M 48G 1% /run
tmpfs 48G 0 48G 0% /sys/fs/cgroup
tmpfs 48G 16K 48G 1% /tmp
/dev/mapper/vg_data-lvdb3 100G 89G 12G 89% /db3
/dev/sda1 477M 260M 188M 59% /boot
/dev/mapper/vg_data-lvdb6 30G 25G 5.9G 81% /db6
/dev/mapper/vg_data-lvdb7 100G 94G 7.0G 94% /db7
/dev/mapper/vg_data-lvcachejrn 180G 52G 129G 29% /cachejrn
/dev/mapper/vg_data-lvdb1 160G 151G 9.1G 95% /db1
/dev/mapper/vg_data-lvcachesys 40G 23G 18G 56% /cachesys
/dev/mapper/vg_data-lvdb2 600G 482G 119G 81% /db2
/dev/mapper/vg_data-lvdb4 240G 197G 44G 82% /db4
/dev/mapper/vg_data-lvdb5 1.2T 1.2T 78G 94% /db5
/dev/mapper/vg_data-lvjrnbackup 40G 35M 40G 1% /jrnbackup
/dev/mapper/vg_data-lvidx_share 13G 2.8G 11G 22% /idx_share
/dev/mapper/vg_data-lvcachealtjrn 5.0G 33M 5.0G 1% /cachealtjrn
/dev/mapper/vg_data-lvdba 2.0G 33M 2.0G 2% /dba
/dev/mapper/vg_data-lvedi 30G 88M 30G 1% /edi
/dev/mapper/rootvg-LogVol02 12G 3.7G 7.2G 34% /var
laxm1151:/ 99G 105M 94G 1% /var/crash
laxm1bnas50:/vol/sapdms1/sapdevdms1 6.7T 5.8T 870G 88% /sapdevdms1
tmpfs 9.5G 0 9.5G 0% /run/user/4005
tmpfs 9.5G 0 9.5G 0% /run/user/2003
tmpfs 9.5G 0 9.5G 0% /run/user/3004
tmpfs 9.5G 0 9.5G 0% /run/user/4002
tmpfs 9.5G 0 9.5G 0% /run/user/1000
laxm1311:/export/trans 935G 268G 620G 31% /usr/sap/trans