diff options
| author | Richard W.M. Jones <rjones@redhat.com> | 2012-07-09 15:23:09 +0100 |
|---|---|---|
| committer | Richard W.M. Jones <rjones@redhat.com> | 2012-07-09 15:23:09 +0100 |
| commit | b749dc70742e749dbd7c0c20e6e7191fdd199170 (patch) | |
| tree | 664c276f59c96186de11f8612ea739351af85807 /fuse/guestmount.pod | |
| parent | bd3e42a8ded1ed7a4177ad03646572eb6155a49c (diff) | |
| download | libguestfs-b749dc70742e749dbd7c0c20e6e7191fdd199170.tar.gz libguestfs-b749dc70742e749dbd7c0c20e6e7191fdd199170.tar.xz libguestfs-b749dc70742e749dbd7c0c20e6e7191fdd199170.zip | |
fuse: Document Device or resource busy errors from fusermount.
Diffstat (limited to 'fuse/guestmount.pod')
| -rw-r--r-- | fuse/guestmount.pod | 17 |
1 files changed, 17 insertions, 0 deletions
diff --git a/fuse/guestmount.pod b/fuse/guestmount.pod index b81c635c..a0bc6f14 100644 --- a/fuse/guestmount.pod +++ b/fuse/guestmount.pod @@ -89,6 +89,23 @@ necessary on Debian and derivatives. On other distros, no special group is required. It is not necessary on Fedora or Red Hat Enterprise Linux. +=head2 fusermount error: "Device or resource busy" + +You can see this error when another process on the system jumps into +the mountpoint you have just created, holding it open and preventing +you from unmounting it. The usual culprits are various GUI "indexing" +programs. + +The popular workaround for this problem is to retry the +C<fusermount -u> command a few times until it works. Unfortunately +this isn't a reliable fix if (for example) the mounted filesystem is +particularly large and the intruding program is persistent. + +A proper fix is to use a private mountpoint by creating a new mount +namespace using the Linux-specific L<clone(2)>/L<unshare(2)> flag +C<CLONE_NEWNS>. Unfortunately at the moment this requires root and we +would also probably need to add it as a feature to guestmount. + =head1 OPTIONS =over 4 |