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

Groups > linux.debian.user > #219285 > unrolled thread

Modern automounters and umount

Back to article view | Back to linux.debian.user

Contents

  Modern automounters and umount "Thomas Schmitt" <scdbackup@gmx.net> - 2020-02-21 09:40 +0100
    Re: Modern automounters and umount Klaus Singvogel <deb-user-ml@singvogel.net> - 2020-02-21 09:50 +0100
      Re: Modern automounters and umount Stefan Monnier <monnier@iro.umontreal.ca> - 2020-02-21 15:00 +0100
        Re: Modern automounters and umount Jonathan Dowland <jon+debian-user@dow.land> - 2020-02-21 16:30 +0100
          Re: Modern automounters and umount Mark Allums <mark@allums.email> - 2020-02-22 05:00 +0100
            Re: Modern automounters and umount Gene Heskett <gheskett@shentel.net> - 2020-02-22 05:50 +0100
              Re: Modern automounters and umount Curt <curty@free.fr> - 2020-02-22 09:50 +0100
              Re: Modern automounters and umount <tomas@tuxteam.de> - 2020-02-22 09:50 +0100
                Re: Modern automounters and umount Stefan Monnier <monnier@iro.umontreal.ca> - 2020-02-22 15:40 +0100
                  Re: Modern automounters and umount <tomas@tuxteam.de> - 2020-02-22 17:10 +0100
                    Re: Modern automounters and umount "Thomas Schmitt" <scdbackup@gmx.net> - 2020-02-22 17:40 +0100
                      Re: Modern automounters and umount <tomas@tuxteam.de> - 2020-02-22 17:50 +0100
                        Re: Modern automounters and umount "Thomas Schmitt" <scdbackup@gmx.net> - 2020-02-22 18:00 +0100
                          Re: Modern automounters and umount <tomas@tuxteam.de> - 2020-02-22 18:10 +0100
                            Re: Modern automounters and umount Gene Heskett <gheskett@shentel.net> - 2020-02-22 19:30 +0100
                              Re: Modern automounters and umount <tomas@tuxteam.de> - 2020-02-22 21:00 +0100
                                Re: Modern automounters and umount Gene Heskett <gheskett@shentel.net> - 2020-02-22 23:50 +0100
            Re: Modern automounters and umount Curt <curty@free.fr> - 2020-02-22 15:40 +0100
              Re: Modern automounters and umount Mark Allums <mark@allums.email> - 2020-02-23 10:40 +0100
                Re: Modern automounters and umount Curt <curty@free.fr> - 2020-02-23 12:10 +0100
                  Re: Modern automounters and umount Mark Allums <maa@allums.com> - 2020-02-24 09:00 +0100
                    Re: Modern automounters and umount Curt <curty@free.fr> - 2020-02-24 12:00 +0100
                      Re: Modern automounters and umount David Wright <deblis@lionunicorn.co.uk> - 2020-02-24 17:10 +0100
                        Re: Modern automounters and umount Curt <curty@free.fr> - 2020-02-24 18:20 +0100
                        Re: Modern automounters and umount Mark Allums <mark@allums.email> - 2020-02-25 08:20 +0100
                          Re: Modern automounters and umount Curt <curty@free.fr> - 2020-02-25 10:50 +0100
                            Re: Modern automounters and umount Mark Allums <mark@allums.email> - 2020-02-25 11:40 +0100
                              Re: Modern automounters and umount Curt <curty@free.fr> - 2020-02-25 15:40 +0100
                              Re: Modern automounters and umount songbird <songbird@anthive.com> - 2020-02-25 19:40 +0100
            Re: Modern automounters and umount Jonathan Dowland <jon+debian-user@dow.land> - 2020-02-23 22:10 +0100
              Re: Modern automounters and umount Mark Allums <mark@allums.email> - 2020-02-24 11:40 +0100
                Re: Modern automounters and umount Jonathan Dowland <jon+debian-user@dow.land> - 2020-02-25 12:00 +0100
          Re: Modern automounters and umount "Thomas Schmitt" <scdbackup@gmx.net> - 2020-02-23 22:40 +0100
    Re: Modern automounters and umount songbird <songbird@anthive.com> - 2020-02-21 22:50 +0100

Page 2 of 2 — ← Prev page 1 [2]

#219383

On 2/23/20 5:00 AM, Curt wrote:
> I never understood the actual procedure for unmounting when gvfsd was
>> doing it;s thing, nor how to prevent the whole mess in the first place
>> (short of doing without gvfsd, et al).
> Well, at any rate, I can only believe your deal here (*completely*
> unrelated to the tool 'undisksctl', BTW, contrary to what some have
> insinuated) is the exact same deal as the one exposed in the thread you
> initiated about a year ago
>
> https://lists.debian.org/debian-user/2019/02/msg00542.html
>
> whose upshot appeared to be
>
>   root@martha:~# lsof /dev/sdb
>   lsof: WARNING: can't stat() fuse.gvfsd-fuse file system
>   /run/user/1001/gvfs
>         Output information may be incomplete.
>
> and in which David Wright advised:
>
>   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.

The gvfsd --no-fuse doesn't do it for me.

[toc] | [prev] | [next] | [standalone]

#219388

On 2020-02-24, Mark Allums <maa@allums.com> wrote:
>>
>>   How to set an environment variable in a DE is left as an exercise for
>>   the reader.
>
> The gvfsd --no-fuse doesn't do it for me.
>

That may be David's exercise then.

-- 
"J'ai pour me guérir du jugement des autres toute la distance qui me sépare de
moi." Antonin Artaud

[toc] | [prev] | [next] | [standalone]

#219396

On Mon 24 Feb 2020 at 10:54:28 (-0000), Curt wrote:
> On 2020-02-24, Mark Allums <maa@allums.com> wrote:
> >>
> >>   How to set an environment variable in a DE is left as an exercise for
> >>   the reader.
> >
> > The gvfsd --no-fuse doesn't do it for me.
> >
> 
> That may be David's exercise then.

I think not. I made my suggestion (exactly a year ago) as I thought
the option, and its corresponding variable, could have been overlooked
on the man page, which was supposed to have been consulted already.

I also wrote on the next day that "Doesn't work" wasn't a response
that carried much information. It's therefore disappointing to read
"doesn't do it for me" this time around.

However, a later post contains:

   george@martha:~$ gvfsd --no-fuse
   bash: gvfsd: command not found
   george@martha:~$ systemctl stop gvfsd
   Failed to stop gvfsd.service: Unit gvfsd.service not loaded.

which suggests a bit of misunderstanding about what gvfsd is.
AIUI it's a daemon (hence the d), and not in anyone's PATH,
which is why you have to find out where it's running from and
what might be consulting the value of GVFS_DISABLE_FUSE.
Also I think the service is called gvfs-daemon (but there may
be other related ones involved).

As for doing exercises, I don't have gvfs* installed, nor any DE,
so I wouldn't know where to start.

Drifting a litle, I do remember being surprised how easy it is for
devices to be mounted twice, having had difficulty myself (mount
would complain the device was already mounted). It turned out that,
because the device I tried using was originally mounted readonly,
I also had to set  ro  in the second mount command for it to succeed.

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#219397

On 2020-02-24, David Wright <deblis@lionunicorn.co.uk> wrote:
>
>
> which suggests a bit of misunderstanding about what gvfsd is.
> AIUI it's a daemon (hence the d), and not in anyone's PATH,
> which is why you have to find out where it's running from and
> what might be consulting the value of GVFS_DISABLE_FUSE.
> Also I think the service is called gvfs-daemon (but there may
> be other related ones involved).

It seems to run from '/usr/lib/gvfs/gvfsd'. 

I don't know whether he tried, simply, "export GVFS_DISABLE_FUSE=1" or
not (and stopped and restarted the daemon by one of the usual methods);
I understood what might consult the value of GVFS_DISABLE_FUSE is the
gvfsd daemon itself.

>From the man:

 gvfsd-fuse is normally started by gvfsd(1). In this case, the mount
 point is $XDG_RUNTIME_DIR/gvfs or $HOME/.gvfs.  

> As for doing exercises, I don't have gvfs* installed, nor any DE,
> so I wouldn't know where to start.
>
> Drifting a litle, I do remember being surprised how easy it is for
> devices to be mounted twice, having had difficulty myself (mount
> would complain the device was already mounted). It turned out that,
> because the device I tried using was originally mounted readonly,
> I also had to set  ro  in the second mount command for it to succeed.
>
> Cheers,
> David.
>
>


-- 
"J'ai pour me guérir du jugement des autres toute la distance qui me sépare de
moi." Antonin Artaud

[toc] | [prev] | [next] | [standalone]

#219414

On 2/24/20 10:08 AM, David Wright wrote:
> On Mon 24 Feb 2020 at 10:54:28 (-0000), Curt wrote:
>> On 2020-02-24, Mark Allums <maa@allums.com> wrote:

> 
>     george@martha:~$ gvfsd --no-fuse
>     bash: gvfsd: command not found
>     george@martha:~$ systemctl stop gvfsd
>     Failed to stop gvfsd.service: Unit gvfsd.service not loaded.
> 
> which suggests a bit of misunderstanding about what gvfsd is.
> AIUI it's a daemon (hence the d), and not in anyone's PATH,
> which is why you have to find out where it's running from and
> what might be consulting the value of GVFS_DISABLE_FUSE.
> Also I think the service is called gvfs-daemon (but there may
> be other related ones involved).

george@martha:~$ systemctl stop gvfs-daemon
Failed to stop gvfs-daemon.service: Unit gvfs-daemon.service not loaded.
george@martha:~$ gvfsd-fuse
bash: gvfsd-fuse: command not found
george@martha:~$ man gvfs-fuse
No manual entry for gvfs-fuse



george@martha:~$ apropos gvfs
gvfs (7)             - GIO virtual file system
gvfs-cat (1)         - (unknown subject)
gvfs-copy (1)        - (unknown subject)
gvfs-info (1)        - (unknown subject)
gvfs-less (1)        - Execute less on the output of gvfs-cat
gvfs-ls (1)          - (unknown subject)
gvfs-mime (1)        - (unknown subject)
gvfs-mkdir (1)       - (unknown subject)
gvfs-monitor-dir (1) - (unknown subject)
gvfs-monitor-file (1) - (unknown subject)
gvfs-mount (1)       - (unknown subject)
gvfs-move (1)        - (unknown subject)
gvfs-open (1)        - (unknown subject)
gvfs-rename (1)      - (unknown subject)
gvfs-rm (1)          - (unknown subject)
gvfs-save (1)        - (unknown subject)
gvfs-set-attribute (1) - (unknown subject)
gvfs-trash (1)       - (unknown subject)
gvfs-tree (1)        - (unknown subject)
gvfsd (1)            - Main daemon for gvfs
gvfsd-fuse (1)       - Fuse daemon for gvfs
gvfsd-metadata (1)   - Metadata daemon for gvfs


> 
> As for doing exercises, I don't have gvfs* installed, nor any DE,
> so I wouldn't know where to start.
> 
> Drifting a litle, I do remember being surprised how easy it is for
> devices to be mounted twice, having had difficulty myself (mount
> would complain the device was already mounted). It turned out that,
> because the device I tried using was originally mounted readonly,
> I also had to set  ro  in the second mount command for it to succeed.
> 
> Cheers,
> David.
> 

Please advise as to the best way to set an environment variable on 
startup before gvfs, et al load.

Mark

[toc] | [prev] | [next] | [standalone]

#219416

On 2020-02-25, Mark Allums <mark@allums.email> wrote:
>
> george@martha:~$ systemctl stop gvfs-daemon
> Failed to stop gvfs-daemon.service: Unit gvfs-daemon.service not loaded.

You cannot stop what does not exist.

I think the systemd unit involved is
 
 run-user-1000-gvfs.mount

Try 'systemctl status run-user-1000-gvfs.mount'
and see.

> george@martha:~$ gvfsd-fuse
> bash: gvfsd-fuse: command not found

This thing isn't in your path, which has been explained.

 /usr/lib/gvfs/gvfsd-fuse

> george@martha:~$ man gvfs-fuse
> No manual entry for gvfs-fuse

It's called 'gvfsd-fuse'.

> Please advise as to the best way to set an environment variable on 
> startup before gvfs, et al load.

A tricky exercise which can depend on your DE (and maybe even your
graphical login manager). What have you tried so far?

> Mark
>
>


-- 
"J'ai pour me guérir du jugement des autres toute la distance qui me sépare de
moi." Antonin Artaud

[toc] | [prev] | [next] | [standalone]

#219419

On 2/25/20 3:43 AM, Curt wrote:
> On 2020-02-25, Mark Allums <mark@allums.email> wrote:
>>
>> george@martha:~$ systemctl stop gvfs-daemon
>> Failed to stop gvfs-daemon.service: Unit gvfs-daemon.service not loaded.
> 
> You cannot stop what does not exist.
> 
> I think the systemd unit involved is
>   
>   run-user-1000-gvfs.mount
> 
> Try 'systemctl status run-user-1000-gvfs.mount'
> and see.

george@martha:~$ systemctl status run-user-1000-gvfs.mount
Unit run-user-1000-gvfs.mount could not be found.


>> george@martha:~$ gvfsd-fuse
>> bash: gvfsd-fuse: command not found
> 
> This thing isn't in your path, which has been explained.
> 
>   /usr/lib/gvfs/gvfsd-fuse
> 
>> george@martha:~$ man gvfs-fuse
>> No manual entry for gvfs-fuse
> 
> It's called 'gvfsd-fuse'.
GVFSD-FUSE(1)                    User Commands 
GVFSD-FUSE(1)

NAME
        gvfsd-fuse - Fuse daemon for gvfs

SYNOPSIS
        gvfsd-fuse PATH

DESCRIPTION
        gvfsd-fuse maintains a fuse mount to make gvfs backends available to
        POSIX applications. The mount point for the fuse filesystem is 
provided
        by the [PATH] argument.

        gvfsd-fuse is normally started by gvfsd(1). In this case, the mount
        point is $XDG_RUNTIME_DIR/gvfs or $HOME/.gvfs.

OPTIONS
        -d
            Enable fuse debug output. This implies -f.

        -f
            Run in the foreground.

        -s
            Run single-threaded.

        -o OPTION
            Set a fuse-specific option. See the fuse documentation for a 
list
            of these.

EXIT STATUS
        On success 0 is returned, a non-zero failure code otherwise.

SEE ALSO
        gvfs(7)

gvfs 
GVFSD-FUSE(1)



>> Please advise as to the best way to set an environment variable on
>> startup before gvfs, et al load.
> 
> A tricky exercise which can depend on your DE (and maybe even your
> graphical login manager). What have you tried so far?

The things I tried are naive.  I don't know, or have forgotten, where to 
put commands that run that early in the process.  I run the latest MATE 
out of Bullseye, 1.24.x-y.  There is a partial installation (a 
"minimal") Gnome 3 installed, and various Gnome-related programs.  XCFE 
is installed, for emergencies.  (I am a bad typist, and am rather 
dependent on GUIs.)  I load MATE by default at startup.

/usr/lib/gvfs/gvfsd --no-fuse
Failed to acquire daemon name, perhaps the VFS daemon is already running?

[toc] | [prev] | [next] | [standalone]

#219425

On 2020-02-25, Mark Allums <mark@allums.email> wrote:
>> 
>> A tricky exercise which can depend on your DE (and maybe even your
>> graphical login manager). What have you tried so far?
>
> The things I tried are naive.  I don't know, or have forgotten, where to 
> put commands that run that early in the process.  I run the latest MATE 
> out of Bullseye, 1.24.x-y.  There is a partial installation (a 
> "minimal") Gnome 3 installed, and various Gnome-related programs.  XCFE 
> is installed, for emergencies.  (I am a bad typist, and am rather 
> dependent on GUIs.)  I load MATE by default at startup.
>
> /usr/lib/gvfs/gvfsd --no-fuse
> Failed to acquire daemon name, perhaps the VFS daemon is already running?
>

 killall gvfsd
 /usr/lib/gvfs/gvfsd --no-fuse &

might do it (for some arbitrary definition of "it"), but IMO you should search
engine around and experiment with setting the environment variable mentioned
previously).





-- 
"J'ai pour me guérir du jugement des autres toute la distance qui me sépare de
moi." Antonin Artaud

[toc] | [prev] | [next] | [standalone]

#219434

Mark Allums wrote:
...
> /usr/lib/gvfs/gvfsd --no-fuse
> Failed to acquire daemon name, perhaps the VFS daemon is already running?

  you sound about as frustrated by this sort of thing as i
was.

  you could try to find out what it is via the gio command
that is being captured and put it in your .bashrc to let it
go when the desktop opens your terminals (i have them saved
as i like them when i'm working on projects so they are 
always here when i boot up the machine).  you can run tty
in each terminal to find out which is the first one and even
use that in your script to only run it the one time.

  the problem i have is when i plug in devices that the
desktop captures even when i tell it to not do anything.
i'm not even sure if this is still a problem or not, but
between udev/udisk2 and gvfs/gio i threw enough hammers
at it all in my script that i got it to go away so it
could then be properly remounted when and where i want it.
you're welcome to take this script and adapt it for your
own uses:

  https://github.com/flowerbug/camera_file

  comments always appreciated.


  songbird

[toc] | [prev] | [next] | [standalone]

#219374

On Fri, Feb 21, 2020 at 09:58:10PM -0600, Mark Allums wrote:
>Explain this, then:
>
>george@martha:~$ udisksctl unmount -b /dev/sdb1
>Unmounted /dev/sdb1.
>george@martha:~$ sudo e2fsck -c -c -k -p -f -C 0 /dev/sdb1
>/dev/sdb1 is in use.
>e2fsck: Cannot continue, aborting.

Can you repeat this, but include the output of "grep sdb1 /proc/mounts"
before the udisksctl invocation, and again after it?

[toc] | [prev] | [next] | [standalone]

#219387

On 2/23/20 3:02 PM, Jonathan Dowland wrote:
> On Fri, Feb 21, 2020 at 09:58:10PM -0600, Mark Allums wrote:
>> Explain this, then:
>>
>> george@martha:~$ udisksctl unmount -b /dev/sdb1
>> Unmounted /dev/sdb1.
>> george@martha:~$ sudo e2fsck -c -c -k -p -f -C 0 /dev/sdb1
>> /dev/sdb1 is in use.
>> e2fsck: Cannot continue, aborting.
> 
> Can you repeat this, but include the output of "grep sdb1 /proc/mounts"
> before the udisksctl invocation, and again after it?
> 

george@martha:~$ grep sdb1 /proc/mounts
/dev/sdb1 /media/george/5913b3d0-eae1-4748-9ce2-d64d4eb21135 ext4 
rw,sync,nosuid,nodev,relatime 0 0
george@martha:~$ udisksctl unmount -b /dev/sdb1
Unmounted /dev/sdb1.
george@martha:~$ grep sdb1 /proc/mounts
george@martha:~$ sudo e2fsck -cckp -f -C 0 /dev/sdb1
/dev/sdb1 is in use.
e2fsck: Cannot continue, aborting.


george@martha:~$ gvfsd --no-fuse
bash: gvfsd: command not found
george@martha:~$ systemctl stop gvfsd
Failed to stop gvfsd.service: Unit gvfsd.service not loaded.
george@martha:~$

[toc] | [prev] | [next] | [standalone]

#219420

On Mon, Feb 24, 2020 at 04:35:32AM -0600, Mark Allums wrote:
>On 2/23/20 3:02 PM, Jonathan Dowland wrote:
>>Can you repeat this, but include the output of "grep sdb1 /proc/mounts"
>>before the udisksctl invocation, and again after it?

Thanks.

>george@martha:~$ grep sdb1 /proc/mounts
>/dev/sdb1 /media/george/5913b3d0-eae1-4748-9ce2-d64d4eb21135 ext4 
>rw,sync,nosuid,nodev,relatime 0 0
>george@martha:~$ udisksctl unmount -b /dev/sdb1
>Unmounted /dev/sdb1.
>george@martha:~$ grep sdb1 /proc/mounts
<nothing>

This shows that the partition was mounted prior to invoking udisksctl
and not afterwards. So udisksctl is doing what it is supposed to.

Your problem which seems orthogonal to udisksctl seems to be better
diagnosed in the sub-thread Curt is participating in. Good luck!

-- 
👱🏻	Jonathan Dowland
🔗	https://jmtd.net

[toc] | [prev] | [next] | [standalone]

#219375

Hi,

  udisksctl -b unmount /dev/sr0
seems to work for the user who has problems with sudo umount.
I write "seems" because feedback is still a bit sparse.

Unmounting by directory name turned out to be too much prone to user
error. I am not sure whether it would work on that system.


Have a nice day :)

Thomas

[toc] | [prev] | [next] | [standalone]

#219310

Thomas Schmitt wrote:
...
> Does anybody here experience similar stubbornness of automounting ?
> If so: How to unmount a DVD without ejecting it ?

  not having done much with DVDs recently i can't say much
about them.  i can say that i really hate having something 
automounted even when i tell the system to not do anything 
with it.

  i've not had a chance to test the recent MATE update to 
see if that is still an issue or not, but it sure did get 
my peeve up.

  my camera was being captured by gio or some other part of 
the desktop and i had ticked all the boxes and options to 
tell the desktop that i didn't want it touched at all when 
i plugged it in.

  in my script i have to do some fiddling around to make 
sure the device is unmounted and then remounted where i want
it (and that it is actually available).  i did get the 
script working and that is where it has to sit for now.  :)

  check to see if some desktop or other system widget has got 
ahold of it (udev, gio, gvfs, udisk2 and no, i don't know all 
other possible names or details about things that might be 
doing this sort of interference).

  good luck!


  songbird

[toc] | [prev] | [standalone]

Page 2 of 2 — ← Prev page 1 [2]

Back to top | Article view | linux.debian.user

csiph-web