[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Can't scan new disk



On 2/20/19 3:20 AM, Alexander V. Makartsev wrote:

Maybe something simple like "lsof" command can shed some light on this problem?
     $ sudo lsof /dev/sdb
     $ sudo lsof /dev/sdb1

root@martha:~# lsof /dev/sdb
lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1001/gvfs
      Output information may be incomplete.
root@martha:~# lsof /dev/sdb1
lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1001/gvfs
      Output information may be incomplete.
root@martha:~#

There you have it. "lsof" command should not output anything if examined object is not in use. I assume that "/dev/sdb1" gets auto-mounted by gvfsd [1] for user with UID 1001. AFAIK GIO and company implements different mounting scheme without involving traditional kernel mounting and allow to restrict mounted devices only for user who mounted them.
So even root user can't access them if they are mounted by other user.
Try to use gio [2] utility to check status and unmount "/dev/sdb1" device.

[1] man gvfsd
[2] man gio

I man'ed them, but I got nothing useful for my trouble. How does one stop gvfsd, or tell it not to mount anything (right now). I'm about mid-grade with Linux skill, and the care and feeding of demons is a little above my pay grade.

root@martha:~# gio mount -u /dev/sdb1
gio: file:///dev/sdb1: Containing mount for file /dev/sdb1 not found
root@martha:~# gio mount -e /dev/sdb1
gio: file:///dev/sdb1: Containing mount for file /dev/sdb1 not found

Any advice as to how to stop the auto-mounter, gvfsd, or fuse, etc. from tying up my disk, or how to get fsck to scan it?

Mark


Reply to: