Problem with mounting nfs shares after sudden poweroutage
by Thomas Korimort from LinuxQuestions.org on (#5NNH0)
Hi!
I am already experiencing this for the second time and i feel that this is a strange issue: I have AMD Ryzen desktop with Debian Bullseye (before Buster) and a JBOD disk tower with four fully occupied slots. On my desktop i mount the 4 disks as NFS shares, which used to work nicely before the most recent sudden power outage. After that the drives had to be checked and the inodes repaired. One disk in use was lost and restored through backup by copying the backup on the repaired disk. I also changed the file permissions and ownership after the copy procedure. After that the mount procedure during system startup happening in /etc/fstab did not mount anymore my nfs shares correctly. Now my mount table looks like this:
My /etc/fstab has this four entries related to the nfs shares
Code:10.10.10.2:/mnt/WD01 /mnt/WD01 nfs rw,auto,nofail 0 0
10.10.10.2:/mnt/WD02 /mnt/WD02 nfs rw,auto,nofail 0 0
10.10.10.2:/mnt/WD03 /mnt/WD03 nfs rw,auto,nofail 0 0
10.10.10.2:/mnt/WD04 /mnt/WD04 nfs rw,auto,nofail 0 0and the actual mount in /proc/mounts lists like this
Code:10.10.10.2:/mnt/WD04 /mnt/WD04 nfs4 rw,relatime,vers=4.2,rsize=524288,wsize=524288,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=10.10.10.1,local_lock=none,addr=10.10.10.2 0 0
10.10.10.2:/mnt/WD03 /mnt/WD03 nfs4 rw,relatime,vers=4.2,rsize=524288,wsize=524288,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=10.10.10.1,local_lock=none,addr=10.10.10.2 0 0
10.10.10.2:/mnt/WD02 /mnt/WD02 nfs4 rw,relatime,vers=4.2,rsize=524288,wsize=524288,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=10.10.10.1,local_lock=none,addr=10.10.10.2 0 0
10.10.10.2:/mnt/WD03 /mnt/WD01 nfs4 rw,relatime,vers=4.2,rsize=524288,wsize=524288,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=10.10.10.1,local_lock=none,addr=10.10.10.2 0 0One can see that /mnt/WD01 gets mounted under /mnt/WD03 and there is no mount entry for /mnt/WD01. What is wrong here? Reboot does not change anything. This strange constellation is carried over from reboot to reboot and i don't know where i can find the file that is jumbled up.
The mount procedure is waiting for 1,5 minutes for mounting WD01 and WD03 suddenly. The drives itself are okay on my nfs server 10.10.10.2 and exportfs also lists ok:
Code:/mnt/WD01 10.10.10.1
/mnt/WD02 10.10.10.1
/mnt/WD03 10.10.10.1
/mnt/WD04 10.10.10.1
/mnt/WD01 192.168.0.0/24
/mnt/WD01 192.168.1.0/24
/mnt/WD01 10.10.10.0/24WD01 is exported into multiple IP adress spaces for my different router and network switch configurations.
Exactly this problem happened to me with my old Debian Buster installation and led to the same problem.
I am already experiencing this for the second time and i feel that this is a strange issue: I have AMD Ryzen desktop with Debian Bullseye (before Buster) and a JBOD disk tower with four fully occupied slots. On my desktop i mount the 4 disks as NFS shares, which used to work nicely before the most recent sudden power outage. After that the drives had to be checked and the inodes repaired. One disk in use was lost and restored through backup by copying the backup on the repaired disk. I also changed the file permissions and ownership after the copy procedure. After that the mount procedure during system startup happening in /etc/fstab did not mount anymore my nfs shares correctly. Now my mount table looks like this:
My /etc/fstab has this four entries related to the nfs shares
Code:10.10.10.2:/mnt/WD01 /mnt/WD01 nfs rw,auto,nofail 0 0
10.10.10.2:/mnt/WD02 /mnt/WD02 nfs rw,auto,nofail 0 0
10.10.10.2:/mnt/WD03 /mnt/WD03 nfs rw,auto,nofail 0 0
10.10.10.2:/mnt/WD04 /mnt/WD04 nfs rw,auto,nofail 0 0and the actual mount in /proc/mounts lists like this
Code:10.10.10.2:/mnt/WD04 /mnt/WD04 nfs4 rw,relatime,vers=4.2,rsize=524288,wsize=524288,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=10.10.10.1,local_lock=none,addr=10.10.10.2 0 0
10.10.10.2:/mnt/WD03 /mnt/WD03 nfs4 rw,relatime,vers=4.2,rsize=524288,wsize=524288,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=10.10.10.1,local_lock=none,addr=10.10.10.2 0 0
10.10.10.2:/mnt/WD02 /mnt/WD02 nfs4 rw,relatime,vers=4.2,rsize=524288,wsize=524288,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=10.10.10.1,local_lock=none,addr=10.10.10.2 0 0
10.10.10.2:/mnt/WD03 /mnt/WD01 nfs4 rw,relatime,vers=4.2,rsize=524288,wsize=524288,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=10.10.10.1,local_lock=none,addr=10.10.10.2 0 0One can see that /mnt/WD01 gets mounted under /mnt/WD03 and there is no mount entry for /mnt/WD01. What is wrong here? Reboot does not change anything. This strange constellation is carried over from reboot to reboot and i don't know where i can find the file that is jumbled up.
The mount procedure is waiting for 1,5 minutes for mounting WD01 and WD03 suddenly. The drives itself are okay on my nfs server 10.10.10.2 and exportfs also lists ok:
Code:/mnt/WD01 10.10.10.1
/mnt/WD02 10.10.10.1
/mnt/WD03 10.10.10.1
/mnt/WD04 10.10.10.1
/mnt/WD01 192.168.0.0/24
/mnt/WD01 192.168.1.0/24
/mnt/WD01 10.10.10.0/24WD01 is exported into multiple IP adress spaces for my different router and network switch configurations.
Exactly this problem happened to me with my old Debian Buster installation and led to the same problem.