using umount with bash wildcard ends in "device is busy" for mount of parent directory about util-linux HOT 4 CLOSED

so it seems like umount ist opening /etc/issue for some reason if a bash wildcard is used and not releasing it.

Well, it's opening /etc/issue because you asked umount to do so. umount never sees the wildcard -- you've essentially run the command:

umount /mnt/issue /mnt/test2

More recent versions of umount have an -R, --recursive flag which makes this a lot simpler. It then becomes a distro problem because Ubuntu 14.04 still ships a rather old util-linux package containing an obsolete umount/mount implementation.

from util-linux.

Thanks for the answer. But is there a way to close the file without rebooting? I still have a running server where it is not possible to remove an logical volume and so an kvm instance because of this issue. :(

Dave Reisner [email protected]:

    so it seems like umount ist opening /etc/issue for some reason if a bash wildcard is used and not releasing it.



  Well, it's opening /etc/issue because you asked umount to do so. umount never sees the wildcard -- you've essentially run the command:

umount /mnt/issue /mnt/test2

  More recent versions of umount have an -R, --recursive flag which makes this a lot simpler. It then becomes a distro problem because Ubuntu 14.04 still ships a rather old util-linux package containing an obsolete umount/mount implementation.


  —
  Reply to this email directly or view it on GitHub.

from util-linux.

I don't see any evidence here to point to that file being "open" as the cause of the umount failure. Moreover:

1. You're not likely to be operating on the symlink itself -- umount and mount generally follow symlinks (as a symlink itself can't be a mountpoint).
2. On exit, a process will always close its file descriptors.

An strace of the failing command would be a good starting spot to debug, but again, this isn't something upstream util-linux will be interested in addressing unless you can reproduce the error with a newer version of umount. The code for the program you're running no longer exists in the git repository (see 65acdc8)

from util-linux.

Thanks Dave for alll the comment. Closing..

from util-linux.