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

Groups > linux.debian.user > #205540

Re: Can't scan new disk

From Mark Allums <mark@allums.email>
Newsgroups linux.debian.user
Subject Re: Can't scan new disk
Date 2019-02-20 10:30 +0100
Message-ID <xtwmt-82O-15@gated-at.bofh.it> (permalink)
References (1 earlier) <xs3Pz-6Do-7@gated-at.bofh.it> <xseL0-4VC-3@gated-at.bofh.it> <xsJlL-4CL-5@gated-at.bofh.it> <xttoB-6nJ-5@gated-at.bofh.it> <xtwmt-82O-11@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw

On 2/20/19 3:19 AM, Curt wrote:
> On 2019-02-20, Mark Allums <mark@allums.email> 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:~#
> 
>>From what I'm reading you'll have to be martha for this and not root
> (*une fois n'est pas coutume*), if martha mounted.

martha is the name of the server.


>>From man mount.fuse:
> 
>   SECURITY
>     The fusermount program is installed set-user-gid to fuse. This is done to
>     allow users from  fuse group to mount their own filesystem implementations.
>     There must however be some limitations, in order to prevent Bad User from doing
>     nasty things.  Currently those limitations are:
> 
>     1.     The user can only mount on a mountpoint, for which it has write permission
> 
>     2.     The mountpoint is not a sticky directory which isn't owned by the user (like /tmp usually
>                is)
> 
>     3.     No other user (including root) can access the contents of the mounted filesystem.
> 
> 

The disk is not mounted.

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