Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Hi Philipp, >>Stopping NFS, unmounting from the DRBD block dev, remounting the lower >>level device and starting NFS again gets things working on the client >>side. So I was wondering what the problem could be? > > As far as I know NFS uses the device number and the inode number to > identify files it its communication protocol. Since you unmont > it from the lower device and mount it on the DRBD device your inode > numbers stay the same, but suddenly you have got an other device number. > > Is this an clear explanation of the issue ? Certainly is. I was thinking along those lines... but wasn't quite sure, as inspection of /var/lib/nfs doesn't show any device numbers anywhere. Any idea if protocol version matters in this case? >>Oh, one last question. I've got: >> >> wfc-timeout 60; >> degr-wfc-timeout 120; # 2 minutes. >> >>yet, when the drbd initscript runs, it just waits forever (although the >>message does say "the timeout for resource X is 60 seconds"). I'm > > Note1: degt-wfc-timeout should usually be smaller than wfc-timout. Okay, thanks. > But yes, it should only wait 60 (or 120) seconds. Maybe you have other > resouces with an infinit wfc-timeout ? I was only using one resource at the time. Perhaps it has something to do with my wfc-timeout being greater than degr-wfc-timeout. I'll test it when I get a chance. Thanks for your help. > -Philipp Regards, Omar Kilani