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


Groups > linux.debian.user > #205539

Re: Can't scan new disk

Path csiph.com!feeder.erje.net!2.eu.feeder.erje.net!news.neodome.net!news.uzoreto.com!aioe.org!bofh.it!news.nic.it!robomod
From "Alexander V. Makartsev" <avbetev@gmail.com>
Newsgroups linux.debian.user
Subject Re: Can't scan new disk
Date Wed, 20 Feb 2019 10:30:01 +0100
Message-ID <xtwmt-82O-9@gated-at.bofh.it> (permalink)
References <xrV5D-1kY-1@gated-at.bofh.it> <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>
X-Original-To debian-user@lists.debian.org
X-Mailbox-Line From debian-user-request@lists.debian.org Wed Feb 20 09:20:44 2019
Old-Return-Path <avbetev@gmail.com>
X-Amavis-Spam-Status No, score=-1.564 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, BODY_8BITS=1.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FOURLA=0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=2, LDO_WHITELIST=-5, LONGWORDS=2.035, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=no autolearn_force=no
X-Policyd-Weight NOT_IN_SBL_XBL_SPAMHAUS=-1.5 CL_IP_EQ_HELO_IP=-2 (check from: .gmail. - helo: .mail-lf1-x142.google. - helo-domain: .google.) FROM/MX_MATCHES_HELO(DOMAIN)=-2; rate: -5.5
Dkim-Signature v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=xQYhoAcXPr8I/UAKsd79f7H+WAHVqxV0+OmqOWPapgU=; b=sJXPxAUffPLj/tiq4ZtqKgS65et3Lpo0k7IYh1WQPs5Ux4cYqQNRRP3EfoKO0M+L1P 1IfKi131GVEb2rJrIFa5WO7dun/pr7kmAfzcGArUH+KRtVR9ImkU8G2iDymArrW1Xvou bmt0RV23YAihSc78qe1kAdhhTLBflGtq+llFH2P0VoVIIg+KJTezGeH7oWTAo6W02Gh8 tqGVfQ+kjsb8fNxScaMdECbF4FmR5SB6QbikzlKiTGwXSbNOh5WfEeGONroDT0eZVZwe jkXqBiutsN8ljaHRcXJXrbWR/+pHlUUkypyppYyyPGBxUt83z0FW9NmRHdEh5Yx4cdzU 8w+g==
X-Google-Dkim-Signature v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=xQYhoAcXPr8I/UAKsd79f7H+WAHVqxV0+OmqOWPapgU=; b=XZqIyb0ryXghxFE0V9mG8rpNa7ofXZpU8oUF9bg1esHKOuUupoH2wRmWrfDoT5KKmR /ZNwcRLckloG0rXx3sH4XnZ+v58pr+4gAsG79KcvQ9WDSyS3gFUIoQJs22V2qfXZGL/P 2ylHO7T981tgUPD3REhxtap05zS14sFtc+SEwYw85pCotU6PiSj0M6m4jQLZnaoS4LZY 9fv3bTR2yywn4hp713Km4w5LClZqPHk5/ZXl6cbvvQmUDPHjRdjpsftOt9Rh6wbFNfcH OMpbcKO/qazfeWFWjSZfg67il5UU6DkWJjVXzxUkFFNfWRL1ZMrnUDhARMFLwVxSjeEZ uy+Q==
X-Gm-Message-State AHQUAual65jgo3ONYDF6PDHNYM/5vanORMgsDDWDwBodTgOriyQgMm2O G4sWf0UmBsTOawwV9Nbt5F5Dtvzo
X-Google-SMTP-Source AHgI3IaEOOrhLKuFRmpJBslkoCCPEv3H0gnfBU5ixNrNf0r1E7AfHtjIMr0gIlmcZTvxjIvHgxK1tg==
X-Received by 2002:ac2:510e:: with SMTP id q14mr17779921lfb.106.1550654429486; Wed, 20 Feb 2019 01:20:29 -0800 (PST)
User-Agent Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.5.1
MIME-Version 1.0
Content-Type multipart/alternative; boundary="------------4B636FF62C42CDC04D4EEBEF"
Content-Language en-US
X-Mailing-List <debian-user@lists.debian.org> archive/latest/745532
List-ID <debian-user.lists.debian.org>
List-URL <https://lists.debian.org/debian-user/>
List-Archive https://lists.debian.org/msgid-search/40a492cd-9cc2-4ff6-08e6-a2715d54441f@gmail.com
Approved robomod@news.nic.it
Lines 213
Organization linux.* mail to news gateway
Sender robomod@news.nic.it
X-Original-Date Wed, 20 Feb 2019 14:20:28 +0500
X-Original-Message-ID <40a492cd-9cc2-4ff6-08e6-a2715d54441f@gmail.com>
X-Original-References <9bf5d89b-3be9-dea2-21cc-5da3f9223963@allums.email> <slrnq6fj6h.2ch.curty@einstein.electron.org> <af31fcc6-1d10-3e9f-a0e6-37e495d89745@allums.email> <2a711551-d824-ebff-0e4d-f989197fe8de@gmail.com> <87f2f04b-16f8-c158-e49c-136ea0d0e96b@allums.email>
Xref csiph.com linux.debian.user:205539

Show key headers only | View raw


[Multipart message — attachments visible in raw view] - view raw

On 20.02.2019 11:16, Mark Allums wrote:
> On 2/17/19 10:59 PM, Alexander V. Makartsev wrote:
>> On 17.02.2019 1:21, Mark Allums wrote:
>>> On 2/16/19 2:41 AM, Curt wrote:
>>>> On 2019-02-15, Mark Allums <mark@allums.email> wrote:
>>>>> I just bought a new backup disk, and I want to check it. It's
>>>>> mounted in
>>>>> a USB dock.
>>>>>
>>>>> Running the following gives an error:
>>>>>
>>>>> root@martha:~# umount /dev/sdb1
>>>>> root@martha:~# e2fsck -c -c -C 0 -f -F -k -p /dev/sdb1
>>>>> /dev/sdb1 is in use.
>>>>> e2fsck: Cannot continue, aborting.
>>>>>
>>>>> What's causing this and how do I fix it?  It's not MATE; I tried
>>>>> rebooting to rescue mode, but that didn't help.
>>>>>
>>>>> Mark
>>>>
>>>> People sometimes recommend 'fuser' in cases like these in order to
>>>> identify processes that might be accessing the drive.
>>>>
>>>> I mean, the message says '/dev/sdb1 is in use.' Perhaps it is indeed.
>>>>
>>>>   fuser -v -m /dev/sdb1
>>>>
>>>> Worth a try, maybe, as no one else seems to have suggested it.
>>>
>>> root@martha:~# fuser -v -m /dev/sdb1
>>> root@martha:~#
>>>
>>> No results.  Thanks.
>>>
>>> Mark
>>>
>> 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

-- 
With kindest regards, Alexander.

⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄⠀⠀⠀⠀ 

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