3 ms·
Worst thing I ever did was cross hard mount NFS volumes across two machines. With a hard NFS mount, the mount will hang until the other machine responds. When
by whartung 5y ago
Worst thing I ever did was cross hard mount NFS volumes across two machines.
With a hard NFS mount, the mount will hang until the other machine responds.
When we had to power cycle the two servers, they would not come up as they were deadlocked waiting for each other. That was exciting.
- patrickdavey 5y agoHow did you fix it?
- jcynix 5y agoBeen there, done that. Ok, a colleague did it, sbkut 30 years ago ;-) IIRC resetting the machine and forcing it to single boot was the solution.
- oneweekwonder 5y agonot op but we recently wanted to mount nfs and the sysadmin was adamant we use automounter[0] instead of fstab because if the nfs mount is not available it can hang the kernel. Not sure if it is true or just sysadmin lore but was interesting enough to learn about a alternative. [0]: https://linux.die.net/man/8/automount https://linux.die.net/man/8/automount
- aleph- 5y agoOh this can definitely happen, had it occur on my system till I started using nofail as a mount option.
- treesknees 5y agoThis is somewhat common in environments with stable power, you basically never have the entire IT system go down and come back up at the same time.
- dsr_ 5y ago"basically never" is guaranteed to happen at a particularly terrible time, and you won't have recovery procedures, because why would you bother?
- bostik 5y agoSpeaking of NFS, ex-coworker had renamed his prior company's servers "notresponding" and "stilltrying". The NFS client logs must have been glorious.