Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #205743

Re: Can't scan new disk

Show all headers | View raw

On Sun 24 Feb 2019 at 08:42:28 (-0600), Mark Allums wrote:
> 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?

The man page suggests that running   gvfsd --no-fuse   or setting a
value to   GVFS_DISABLE_FUSE   will stop it running.

How to set an environment variable in a DE is left as an exercise for
the reader.

Cheers,
David.

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Can't scan new disk Mark Allums <mark@allums.email> - 2019-02-16 00:30 +0100
  Re: Can't scan new disk deb <deb@rangingthoughts.org> - 2019-02-16 01:10 +0100
    Re: Can't scan new disk Mark Allums <mark@allums.email> - 2019-02-16 02:50 +0100
  Re: Can't scan new disk songbird <songbird@anthive.com> - 2019-02-16 01:30 +0100
    Re: Can't scan new disk Mark Allums <mark@allums.email> - 2019-02-16 02:50 +0100
  Re: Can't scan new disk David Christensen <dpchrist@holgerdanske.com> - 2019-02-16 04:20 +0100
    Re: Can't scan new disk Mark Allums <mark@allums.email> - 2019-02-16 21:40 +0100
      Re: Can't scan new disk David Christensen <dpchrist@holgerdanske.com> - 2019-02-16 23:20 +0100
        Re: Can't scan new disk Mark Allums <mark@allums.email> - 2019-02-18 04:20 +0100
          Re: Can't scan new disk David Christensen <dpchrist@holgerdanske.com> - 2019-02-19 00:40 +0100
        Re: Can't scan new disk Celejar <celejar@gmail.com> - 2019-02-19 19:00 +0100
          Re: Can't scan new disk David Christensen <dpchrist@holgerdanske.com> - 2019-02-20 03:50 +0100
            Re: Can't scan new disk Celejar <celejar@gmail.com> - 2019-02-20 04:30 +0100
              Re: Can't scan new disk David Christensen <dpchrist@holgerdanske.com> - 2019-02-20 06:30 +0100
                Re: Can't scan new disk Celejar <celejar@gmail.com> - 2019-02-20 14:20 +0100
  Re: Can't scan new disk Curt <curty@free.fr> - 2019-02-16 09:50 +0100
    Re: Can't scan new disk Mark Allums <mark@allums.email> - 2019-02-16 21:30 +0100
      Re: Can't scan new disk "Alexander V. Makartsev" <avbetev@gmail.com> - 2019-02-18 06:10 +0100
        Re: Can't scan new disk Mark Allums <mark@allums.email> - 2019-02-20 07:20 +0100
          Re: Can't scan new disk Curt <curty@free.fr> - 2019-02-20 10:30 +0100
            Re: Can't scan new disk Mark Allums <mark@allums.email> - 2019-02-20 10:30 +0100
              Re: Can't scan new disk Curt <curty@free.fr> - 2019-02-20 11:30 +0100
          Re: Can't scan new disk "Alexander V. Makartsev" <avbetev@gmail.com> - 2019-02-20 10:30 +0100
            Re: Can't scan new disk Mark Allums <mark@allums.email> - 2019-02-20 10:50 +0100
              Re: Can't scan new disk "Thomas Schmitt" <scdbackup@gmx.net> - 2019-02-20 11:30 +0100
            Re: Can't scan new disk Curt <curty@free.fr> - 2019-02-20 13:20 +0100
            Re: Can't scan new disk Mark Allums <mark@allums.email> - 2019-02-24 15:50 +0100
              Re: Can't scan new disk David Christensen <dpchrist@holgerdanske.com> - 2019-02-24 21:30 +0100
                Re: Can't scan new disk David Wright <deblis@lionunicorn.co.uk> - 2019-02-24 23:10 +0100
                Re: Can't scan new disk David Christensen <dpchrist@holgerdanske.com> - 2019-02-25 01:10 +0100
                Re: Can't scan new disk Linux-Fan <Ma_Sys.ma@web.de> - 2019-02-25 12:40 +0100
                Re: Can't scan new disk Mark Allums <mark@allums.email> - 2019-02-25 15:20 +0100
                Re: Can't scan new disk Curt <curty@free.fr> - 2019-02-25 15:50 +0100
                Re: Can't scan new disk Mark Allums <mark@allums.email> - 2019-02-25 16:00 +0100
                Re: Can't scan new disk David Wright <deblis@lionunicorn.co.uk> - 2019-02-25 16:30 +0100
                Re: Can't scan new disk <tomas@tuxteam.de> - 2019-02-26 09:30 +0100
              Re: Can't scan new disk David Wright <deblis@lionunicorn.co.uk> - 2019-02-24 23:10 +0100
              Re: Can't scan new disk "Alexander V. Makartsev" <avbetev@gmail.com> - 2019-02-25 20:20 +0100
          Re: Can't scan new disk Jude DaShiell <jdashiel@panix.com> - 2019-02-20 18:40 +0100

csiph-web