Description of problem:I have a number of directories nfs mounted on a machine called charge, from one called info. I had to bring down info and although I thought i had unmounted all of the files on charge, I had not. When I rebooted info, it was impossible to remount the files on charge. when I tried, I kept getting the error message that the nfs mounts were stale. Running mount said that those mounts were (dead). and they were listed as such in proc/mounts. I tried to bring down nfs (service nfs-common stop) and back up. Made no difference. I could not unmount those files, since they were not mounted. and I could not mount them because they were stale. (the reboot froze on something in the startup scripts, and since going to systemd it is totally impossible to figure out on what it froze or how to stop the misbehaving service, but that is another rant for another time). Version-Release number of selected component (if applicable): How reproducible: I have only dared try it once so far, since fixing it took 3 hours I could far more profitably use elsewhere). Steps to Reproduce: 1. 2. 3. Reproducible: Steps to Reproduce:
You should have tried "umount -l" on those NFS mount points. Or you should have mounted them with the soft,intr options in the first place.
CC: (none) => thierry.vignaud
They were mounted with soft,intr eg diskhost9:/local/unruhhome /disk9/home nfs rw,rsize=8192,wsize=8192,soft,bg,intr 0 0 I did not try umount -l, but as far as I know they were not busy at the time the nfs host crashed. What happened was that when the nfs host crashed, another machine was brought up which was a copy of the nfs host, acting as a backup. This was up for about 20 min, when the first nfs host was brought back online. It was at this point that a mount -a was attemped on the machine, which gave stale nfs handles error message, and the symptoms described above.
umount -l enables to kill recalcitrant fses so I think it would have helped here
Happened again. I had to bring down the server info, and did a umount -a -t nfs on all the machines. I then rebooted and brought everything back up and did a mount -a on all the client machines. On the Mageia 2 machine I got a stale nfs handle error. charge[root]>mount -a mount.nfs: /var/spool/mail is busy or already mounted mount.nfs: /disk11/home is busy or already mounted mount.nfs: Stale NFS file handle charge[root]>umount -f /var/lib/texmf umount2: Stale NFS file handle umount: /var/lib/texmf: Stale NFS file handle charge[root]>umount -l /var/lib/texmf umount: /var/lib/texmf: Stale NFS file handle charge[root] mount .... info:/var/lib/texmf on /var/lib/texmf (deleted) type nfs4 (rw,relatime,vers=4.0,rsize=8192,wsize=8192,namlen=255,soft,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=142.103.234.37,local_lock=none,addr=142.103.234.23) I cannot get rid of it and I cannot remount it. (The server is Mandrake 2010.2) I do not want to reboot it. I should not have to reboot (charge the client). But I have no idea how to solve this and it is a bug Also ls -l /var/lib gives d????????? ? ? ? ? ? texmf
CC: (none) => guillomovitch
This message is a reminder that Mageia 2 is nearing its end of life. Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- The Mageia Bugsquad
Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => OLD