Skip to main content
Unix & Linux

Return to Question

Tweeted twitter.com/StackUnix/status/1033006540561833984
added 38 characters in body
Source Link
robert
robert
  • 661
  • 2
  • 9
  • 18

I have mounted /dev and immediately tried to unmount:

$ sudo mount -o rbind /dev m $ sudo umount m umount: /tmp/m: target is busy. $ sudo lsof m lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs Output information may be incomplete. COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME kdevtmpfs 55 root cwd DIR 0,6 4420 2 m kdevtmpfs 55 root rtd DIR 0,6 4420 2 m

I have read that fuser can kill processes accessing the mount point, but I would like to understand what is happening in this simple case. Acording to the lsof output does something use the mountpoint as current working directory (cwd)?

I do not want to use lazy unmount.

I have mounted /dev and immediately tried to unmount:

$ sudo mount -o rbind /dev m $ sudo umount m umount: /tmp/m: target is busy. $ sudo lsof m lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs Output information may be incomplete. COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME kdevtmpfs 55 root cwd DIR 0,6 4420 2 m kdevtmpfs 55 root rtd DIR 0,6 4420 2 m

I have read that fuser can kill processes accessing the mount point, but I would like to understand what is happening in this simple case. Acording to the lsof output does something use the mountpoint as current working directory (cwd)?

I have mounted /dev and immediately tried to unmount:

$ sudo mount -o rbind /dev m $ sudo umount m umount: /tmp/m: target is busy. $ sudo lsof m lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs Output information may be incomplete. COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME kdevtmpfs 55 root cwd DIR 0,6 4420 2 m kdevtmpfs 55 root rtd DIR 0,6 4420 2 m

I have read that fuser can kill processes accessing the mount point, but I would like to understand what is happening in this simple case. Acording to the lsof output does something use the mountpoint as current working directory (cwd)?

I do not want to use lazy unmount.

Source Link
robert
robert
  • 661
  • 2
  • 9
  • 18

umount: target is busy

I have mounted /dev and immediately tried to unmount:

$ sudo mount -o rbind /dev m $ sudo umount m umount: /tmp/m: target is busy. $ sudo lsof m lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs Output information may be incomplete. COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME kdevtmpfs 55 root cwd DIR 0,6 4420 2 m kdevtmpfs 55 root rtd DIR 0,6 4420 2 m

I have read that fuser can kill processes accessing the mount point, but I would like to understand what is happening in this simple case. Acording to the lsof output does something use the mountpoint as current working directory (cwd)?