On Mon, 1 Sep 2014 21:53:30 -0700 John Jason Jordan <[email protected]> dijo:
>>This could be a shell where you did a cd into the share, it could be >>a background process you have running, or a background sub-process for >>an application you are using. >> >>Try using lsof (list open files) as root with the path you are trying >>to umount. This should give you the PID of whatever is holding the >>device open, and from there you can determine how to resolve the >>problem so you can unmount the share. >lsof command on the desktop also hangs, the same as trying ls on >the /media/jjj directory. Trying to view the /media/jjj directory in >Thunar also hangs Thunar. > >I did discover a clue: The GUI task manager on the desktop shows the >mount command twice, and I cannot kill either one (no permission). The >mount command is "sudo mount.nfs >192.168.0.126:/media /media/jjj/Devil-Bonobo/ -o rw," where ...126 is >the laptop. How do you kill a mount command? This morning I got a message from Ubuntu that there were updates for 12.04 on the desktop, which included a new kernel. Knowing that this would require a reboot I decided to apply them and reboot, hoping that the reboot would solve my problems. After rebooting the share is no longer mounted. But the mount command hangs. I stopped it with Ctrl-z, which resulted in "stopped [mount command], but I note that now I have the mount command running in task manager. From past experience, when the mount command hangs it just stays hanging regardless of how long I leave it. An error message would be helpful, but I get nada. However, the umount command now properly says the share is not mounted, rather than "device is busy." _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
