On 2014-12-02 01:17, Greg Freemyer wrote:
On Mon, Dec 1, 2014 at 6:55 PM, Bernhard Voelker <> wrote:
I can't say I use use fuser -m all that often, but I'm pretty sure I have used it with a block device before.
I just tried. I plugged a usb stick, mounted it, and tried: Telcontar:~ # mount /dev/sdh1 /mnt/tmp Telcontar:~ # fuser -m /dev/sdh1 /dev/sdh1: 1 307 369 393 748 937 1025 1027 1028 1029 1033 1036 1037 1038 1039 1040 1086 1477 1480 1657 ... and several lines. But: Telcontar:~ # fuser -m /mnt/tmp Telcontar:~ # Telcontar:~ # fuser /dev/sdh1 Telcontar:~ # which is correct. Now I open a file in that stick with "less", and try again: Telcontar:~ # fuser /dev/sdh1 Telcontar:~ # lsof /dev/sdh1 lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs Output information may be incomplete. lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /var/run/user/1000/gvfs Output information may be incomplete. COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME less 3242 cer 4r REG 8,113 734421674 12 /mnt/tmp/Doctor.Mateo...avi Telcontar:~ # fuser -m /mnt/tmp /mnt/tmp: 3242 Telcontar:~ # See? A single process. But "fuser -m /dev/sdh1" still gives a long and incorrect list. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)