Data backup- (udev problem)

[Angelo Moreschini]

hi,

in order to backing up of the data , I wrote a script that uses the rsync
command.

This script have to be launched manually, and the data are saved on a USB
Hard Disk, which (obviously) must be mounted.

The mounting  of the partitions for the back up on the USB HD is  made
permantly at boot of the computer (the name of the backup-partitions is
wrote in the file / etc / fstab) :

UUID=376214F24CC07CE0 /media/BKx_data-personal ntfs defaults 0 0

UUID=479F99A324FF4D1D /media/BKx_programming ntfs defaults 0 0

UUID=EA8266EA8266BB29 /media/BKx_data-common ntfs defaults 0 0

This script works fine.

However, this solution for backing up the data is problematic, because *I
always receive messages with the request of access to the partitions ** of
the “backup-partitions”** by "nautilus"* - every time that I use the "find"
command.

I can consider that this problem is connected with the *permanent *
*mounting* of the partitions on the HD-USB (on the file /etc/fstab).

To avoid these problems I actually removed the permanent mounting of the
partitions by registering them on the file fstab and now I'm looking for an
alternative solution for the back up the data.

I think this solution can go in the following directions:

-

mounting the partitions (commanded by the script) before executing the
   rsync command and unmounting them immediately afterwards.
   -

alternatively, giving appropriate orders to the “udev feature” about the
   backup partitions (I think this is possible to do, but I do not know how to
   do it).

I would like to have some suggestions and advice about it.
Regards
Angelo

[Bob Marcan]

On Wed, 27 Dec 2017 11:24:06 +0200
Angelo Moreschini  wrote:
> hi,
>
> in order to backing up of the data , I wrote a script that uses the rsync
> command.
>
> This script have to be launched manually, and the data are saved on a USB
> Hard Disk, which (obviously) must be mounted.
>
> The mounting  of the partitions for the back up on the USB HD is  made
> permantly at boot of the computer (the name of the backup-partitions is
> wrote in the file / etc / fstab) :
>
> UUID=376214F24CC07CE0 /media/BKx_data-personal ntfs defaults 0 0
>
> UUID=479F99A324FF4D1D /media/BKx_programming ntfs defaults 0 0
>
> UUID=EA8266EA8266BB29 /media/BKx_data-common ntfs defaults 0 0
>
> This script works fine.
>
> However, this solution for backing up the data is problematic, because *I
> always receive messages with the request of access to the partitions ** of
> the “backup-partitions”** by "nautilus"* - every time that I use the "find"
> command.
>
> I can consider that this problem is connected with the *permanent *
> *mounting* of the partitions on the HD-USB (on the file /etc/fstab).
>
> To avoid these problems I actually removed the permanent mounting of the
> partitions by registering them on the file fstab and now I'm looking for an
> alternative solution for the back up the data.
>
> I think this solution can go in the following directions:
>
> mounting the partitions (commanded by the script) before executing the
>    rsync command and unmounting them immediately afterwards.
>
> alternatively, giving appropriate orders to the “udev feature” about the
>    backup partitions (I think this is possible to do, but I do not know how to
>    do it).
>
> I would like to have some suggestions and advice about it.
> Regards
> Angelo

man autofs
I'm using it.
BR, Bob

[Angelo Moreschini]

thank you  Bob,

I wont try your suggestion, but I have not installed autoff on Fedora 21 :
------
[angelo_dev@localhost ~]$ sudo systemctl status autofs.service
[sudo] password for angelo_dev:
● autofs.service
   Loaded: not-found (Reason: No such file or directory)
   Active: inactive (dead)
-----

So before to do something wrong I would ask you how I can install it (I
didn't find help in this way..)
*It is a autofs repository for Fedora ?*

thank you

Angelo

On Wed, Dec 27, 2017 at 5:38 PM, Bob Marcan  wrote:
> On Wed, 27 Dec 2017 11:24:06 +0200
> Angelo Moreschini  wrote:
> > hi,
> >
> > in order to backing up of the data , I wrote a script that uses the rsync
> > command.
> >
> > This script have to be launched manually, and the data are saved on a USB
> > Hard Disk, which (obviously) must be mounted.
> >
> > The mounting  of the partitions for the back up on the USB HD is  made
> > permantly at boot of the computer (the name of the backup-partitions is
> > wrote in the file / etc / fstab) :
> >
> > UUID=376214F24CC07CE0 /media/BKx_data-personal ntfs defaults 0 0
> >
> > UUID=479F99A324FF4D1D /media/BKx_programming ntfs defaults 0 0
> >
> > UUID=EA8266EA8266BB29 /media/BKx_data-common ntfs defaults 0 0
> >
> > This script works fine.
> >
> > However, this solution for backing up the data is problematic, because *I
> > always receive messages with the request of access to the partitions **
>
> of
> > the “backup-partitions”** by "nautilus"* - every time that I use the
>
> "find"
> > command.
> >
> > I can consider that this problem is connected with the *permanent *
> > *mounting* of the partitions on the HD-USB (on the file /etc/fstab).
> >
> > To avoid these problems I actually removed the permanent mounting of the
> > partitions by registering them on the file fstab and now I'm looking for
>
> an
> > alternative solution for the back up the data.
> >
> > I think this solution can go in the following directions:
> >
> > mounting the partitions (commanded by the script) before executing the
> >    rsync command and unmounting them immediately afterwards.
> >
> > alternatively, giving appropriate orders to the “udev feature” about
>
> the
> > backup partitions (I think this is possible to do, but I do not know
>
> how to
> > do it).
> >
> > I would like to have some suggestions and advice about it.
> > Regards
> > Angelo
>
> man autofs
> I'm using it.
> BR, Bob
> _______________________________________________
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]

[Bob Marcan]

On Sat, 30 Dec 2017 19:26:01 +0200
Angelo Moreschini  wrote:
> thank you  Bob,
> I wont try your suggestion, but I have not installed autoff on Fedora 21 :
>
> [angelo_dev@localhost ~]$ sudo systemctl status autofs.service
> [sudo] password for angelo_dev:
> ● autofs.service
>    Loaded: not-found (Reason: No such file or directory)
>    Active: inactive (dead)
>
> So before to do something wrong I would ask you how I can install it (I
> didn't find help in this way..)
> *It is a autofs repository for Fedora ?*
>
> thank you
>
> Angelo

$ dnf info autofs
Last metadata expiration check: 0:02:07 ago on Thu Jan  4 19:10:02 2018.
Installed Packages
Name         : autofs
Epoch        : 1
Version      : 5.1.2
Release      : 2.fc26
Arch         : x86_64
Size         : 3.5 M
Source       : autofs-5.1.2-2.fc26.src.rpm
Repo         : @System
From repo    : @commandline
Summary      : A tool for automatically mounting and unmounting filesystems
License      : GPLv2+
Description  : autofs is a daemon which automatically mounts filesystems when
             : you use them, and unmounts them later when you are not using
             : them.  This can include network filesystems, CD-ROMs, floppies,
             : and so forth.

BR, Bob

[Samuel Sieb]

On 12/27/2017 01:24 AM, Angelo Moreschini wrote:
> However, this solution for backing up the data is problematic, because 
> _I always receive messages with the request of access to the partitions 
> __of the “backup-partitions”__by "nautilus"_ - every time that I use the 
> "find" command.

I don't understand this.  Can you provide more details about what is 
happening here?  I wonder if systemd is lazy mounting the drives, so 
they don't actually mount until you access them for the first time.  If 
you look in the journal, you should be able to tell by the timestamps 
when the drive gets mounted.

[Angelo Moreschini]

Hi Samuel,

if I use fstab to *mount permanently* some partitions that I made on a USB
Hard Disk, *THEN, every time* I use the "find" command, I get (from
nautilus) requests to open (show) these partitions.

And this is not only an (very much) annoying problem..
In that eventuality I also begin  to have problems at the boot  ...
I not understand exactly because of this (I can only to think the problem
is connected with the <udev> feature) ,
*but for sure*..  the problems completely disappear if I delete the
permanent mounting of partitions with fstab.

================
*here some line of command* :  *sudo journalctl  | grep -i
PRTZ_programming* *(PRTZ_programming
= name of partition I made on USB HD)*

Nov 12 09:29:50 localhost.pluto gnome-session[1798]: Gjs-Message: JS LOG:
Unable to mount volume PRTZ_programming: Gio.IOErrorEnum: Error mounting
system-managed device /dev/sdb2: Command-line `mount
"/media/BKx_programming"' exited with non-zero exit status 18: Failed to
write lock '/dev/sdb2': Resource temporarily unavailable
Nov 12 09:29:55 localhost.pluto gnome-session[1798]: Gjs-Message: JS LOG:
Unable to mount volume PRTZ_programming: Gio.IOErrorEnum: Error mounting
system-managed device /dev/sdb2: Command-line `mount
"/media/BKx_programming"' exited with non-zero exit status 18: Failed to
write lock '/dev/sdb2': Resource temporarily unavailable
Nov 12 09:29:57 localhost.pluto ntfs-3g[5657]: Mounted /dev/sdb2
(Read-Write, label "PRTZ_programming", NTFS 3.1)
Nov 12 09:31:08 localhost.pluto ntfs-3g[5657]: Unmounting /dev/sdb2
(PRTZ_programming)
Nov 12 11:02:54 localhost.pluto ntfs-3g[691]: Mounted /dev/sdb2
(Read-Write, label "PRTZ_programming", NTFS 3.1)
Nov 12 19:59:58 localhost.pluto ntfs-3g[691]: Unmounting /dev/sdb2
(PRTZ_programming)
Nov 13 08:14:05 localhost.pluto ntfs-3g[697]: Mounted /dev/sdb2
(Read-Write, label "PRTZ_programming", NTFS 3.1)
Nov 13 08:14:33 localhost.pluto ntfs-3g[697]: Unmounting /dev/sdb2
(PRTZ_programming)
Nov 13 08:14:37 localhost.pluto ntfs-3g[1735]: Mounted /dev/sdb2
(Read-Write, label "PRTZ_programming", NTFS 3.1)
Nov 13 19:31:44 localhost.pluto ntfs-3g[1735]: Unmounting /dev/sdb2
(PRTZ_programming)
Nov 14 17:36:56 localhost.pluto ntfs-3g[669]: Mounted /dev/sdb2
(Read-Write, label "PRTZ_programming", NTFS 3.1)
Nov 14 20:37:52 localhost.pluto ntfs-3g[669]: Unmounting /dev/sdb2
(PRTZ_programming)
Nov 15 06:49:27 localhost.pluto ntfs-3g[699]: Mounted /dev/sdb2
(Read-Write, label "PRTZ_programming", NTFS 3.1)
Nov 15 06:52:00 localhost.pluto ntfs-3g[842]: Mounted /dev/sdb2
(Read-Write, label "PRTZ_programming", NTFS 3.1)
Nov 15 06:53:14 localhost.pluto ntfs-3g[724]: Mounted /dev/sdb2
(Read-Write, label "PRTZ_programming", NTFS 3.1)
Nov 15 06:53:47 localhost.pluto ntfs-3g[724]: Unmounting /dev/sdb2
(PRTZ_programming)
Nov 15 06:53:51 localhost.pluto ntfs-3g[1701]: Mounted /dev/sdb2
(Read-Write, label "PRTZ_programming", NTFS 3.1)
Nov 15 07:40:48 localhost.pluto ntfs-3g[1701]: Unmounting /dev/sdb2
(PRTZ_programming)
Nov 20 10:33:09 localhost.pluto ntfs-3g[8140]: Mounted /dev/sdb2
(Read-Write, label "PRTZ_programming", NTFS 3.1)
Nov 20 10:33:09 localhost.pluto udisksd[1506]: Mounted /dev/sdb2 at
/run/media/angelo_dev/PRTZ_programming on behalf of uid 1003
Nov 20 10:33:09 localhost.pluto org.gtk.Private.UDisks2VolumeMonitor[1729]:
index_parse.c:191: indx_parse(): error opening /run/media/angelo
================l

I use the partitions on USB Hard Disk in order to do the back up of the
data of the computer..
And now I am looking for an alternative method (solution) to mounting the
partitions..

-----------------
another thing I would like to ask :
to use autofs for partitions on my USB HD that is permanently connected to
computer,
it is mandatory install also NFS (network file system)  ???
-----------------
Thank you

Angelo

On Fri, Jan 5, 2018 at 12:19 AM, Samuel Sieb  wrote:
> On 12/27/2017 01:24 AM, Angelo Moreschini wrote:
> > However, this solution for backing up the data is problematic, because _I
> > always receive messages with the request of access to the partitions __of
> > the “backup-partitions”__by "nautilus"_ - every time that I use the "find"
> > command.
>
> I don't understand this.  Can you provide more details about what is
> happening here?  I wonder if systemd is lazy mounting the drives, so they
> don't actually mount until you access them for the first time.  If you look
> in the journal, you should be able to tell by the timestamps when the drive
> gets mounted.
>
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]

[Angelo Moreschini]

*other lines of journalctl  that report errors *

Jan 01 12:38:12 localhost.pluto org.gtk.Private.UDisks2VolumeMonitor[2153]:
index_parse.c:191: indx_parse(): *error* opening
/run/media/angelo_dev/PRTZ_programming/BDMV/BACKUP/index.bdmv
Jan 01 13:00:02 localhost.pluto ntfs-3g[7860]: Unmounting /dev/sdb2
(PRTZ_programming)
Jan 02 07:50:11 localhost.pluto ntfs-3g[2308]: Mounted /dev/sdb2
(Read-Write, label "PRTZ_programming", NTFS 3.1)
Jan 02 07:50:11 localhost.pluto udisksd[1558]: Mounted /dev/sdb2 at
/run/media/angelo_dev/PRTZ_programming on behalf of uid 1003
Jan 02 07:50:11 localhost.pluto org.gtk.Private.UDisks2VolumeMonitor[1891]:
index_parse.c:191: indx_parse(): *error* opening
/run/media/angelo_dev/PRTZ_programming/BDMV/index.bdmv
Jan 02 07:50:11 localhost.pluto org.gtk.Private.UDisks2VolumeMonitor[1891]:
index_parse.c:191: indx_parse(): *error* opening
/run/media/angelo_dev/PRTZ_programming/BDMV/BACKUP/index.bdmv
Jan 02 12:07:40 localhost.pluto ntfs-3g[2308]: Unmounting /dev/sdb2
(PRTZ_programming)
Jan 02 12:08:28 localhost.pluto ntfs-3g[690]: Mounted /dev/sdb2
(Read-Write, label "PRTZ_programming", NTFS 3.1)
Jan 02 12:12:33 localhost.pluto ntfs-3g[690]: Unmounting /dev/sdb2
(PRTZ_programming)

*other lines of journalctl  that report the word gnome*

Jan 02 19:57:06 localhost.pluto *gnome*-session[1803]: Gjs-Message: JS LOG:
Unable to mount volume PRTZ_programming: Gio.IOErrorEnum: Error mounting
system-managed device /dev/sdb2: Command-line `mount
"/media/BKx_programming"' exited with non-zero exit status 18: Failed to
write lock '/dev/sdb2': Resource temporarily unavailable

On Fri, Jan 5, 2018 at 10:13 AM, Angelo Moreschini <
[e-mail]> wrote:
> Hi Samuel,
>
> if I use fstab to *mount permanently* some partitions that I made on a
> USB Hard Disk, *THEN, every time* I use the "find" command, I get (from
> nautilus) requests to open (show) these partitions.
>
> And this is not only an (very much) annoying problem..
> In that eventuality I also begin  to have problems at the boot  ...
> I not understand exactly because of this (I can only to think the problem
> is connected with the <udev> feature) ,
> *but for sure*..  the problems completely disappear if I delete the
> permanent mounting of partitions with fstab.
>
> ================
> *here some line of command* :  *sudo journalctl  | grep -i
> PRTZ_programming* *(PRTZ_programming = name of partition I made on USB
> HD)*
>
> Nov 12 09:29:50 localhost.pluto gnome-session[1798]: Gjs-Message: JS LOG:
> Unable to mount volume PRTZ_programming: Gio.IOErrorEnum: Error mounting
> system-managed device /dev/sdb2: Command-line `mount
> "/media/BKx_programming"' exited with non-zero exit status 18: Failed to
> write lock '/dev/sdb2': Resource temporarily unavailable
> Nov 12 09:29:55 localhost.pluto gnome-session[1798]: Gjs-Message: JS LOG:
> Unable to mount volume PRTZ_programming: Gio.IOErrorEnum: Error mounting
> system-managed device /dev/sdb2: Command-line `mount
> "/media/BKx_programming"' exited with non-zero exit status 18: Failed to
> write lock '/dev/sdb2': Resource temporarily unavailable
> Nov 12 09:29:57 localhost.pluto ntfs-3g[5657]: Mounted /dev/sdb2
> (Read-Write, label "PRTZ_programming", NTFS 3.1)
> Nov 12 09:31:08 localhost.pluto ntfs-3g[5657]: Unmounting /dev/sdb2
> (PRTZ_programming)
> Nov 12 11:02:54 localhost.pluto ntfs-3g[691]: Mounted /dev/sdb2
> (Read-Write, label "PRTZ_programming", NTFS 3.1)
> Nov 12 19:59:58 localhost.pluto ntfs-3g[691]: Unmounting /dev/sdb2
> (PRTZ_programming)
> Nov 13 08:14:05 localhost.pluto ntfs-3g[697]: Mounted /dev/sdb2
> (Read-Write, label "PRTZ_programming", NTFS 3.1)
> Nov 13 08:14:33 localhost.pluto ntfs-3g[697]: Unmounting /dev/sdb2
> (PRTZ_programming)
> Nov 13 08:14:37 localhost.pluto ntfs-3g[1735]: Mounted /dev/sdb2
> (Read-Write, label "PRTZ_programming", NTFS 3.1)
> Nov 13 19:31:44 localhost.pluto ntfs-3g[1735]: Unmounting /dev/sdb2
> (PRTZ_programming)
> Nov 14 17:36:56 localhost.pluto ntfs-3g[669]: Mounted /dev/sdb2
> (Read-Write, label "PRTZ_programming", NTFS 3.1)
> Nov 14 20:37:52 localhost.pluto ntfs-3g[669]: Unmounting /dev/sdb2
> (PRTZ_programming)
> Nov 15 06:49:27 localhost.pluto ntfs-3g[699]: Mounted /dev/sdb2
> (Read-Write, label "PRTZ_programming", NTFS 3.1)
> Nov 15 06:52:00 localhost.pluto ntfs-3g[842]: Mounted /dev/sdb2
> (Read-Write, label "PRTZ_programming", NTFS 3.1)
> Nov 15 06:53:14 localhost.pluto ntfs-3g[724]: Mounted /dev/sdb2
> (Read-Write, label "PRTZ_programming", NTFS 3.1)
> Nov 15 06:53:47 localhost.pluto ntfs-3g[724]: Unmounting /dev/sdb2
> (PRTZ_programming)
> Nov 15 06:53:51 localhost.pluto ntfs-3g[1701]: Mounted /dev/sdb2
> (Read-Write, label "PRTZ_programming", NTFS 3.1)
> Nov 15 07:40:48 localhost.pluto ntfs-3g[1701]: Unmounting /dev/sdb2
> (PRTZ_programming)
> Nov 20 10:33:09 localhost.pluto ntfs-3g[8140]: Mounted /dev/sdb2
> (Read-Write, label "PRTZ_programming", NTFS 3.1)
> Nov 20 10:33:09 localhost.pluto udisksd[1506]: Mounted /dev/sdb2 at
> /run/media/angelo_dev/PRTZ_programming on behalf of uid 1003
> Nov 20 10:33:09 localhost.pluto org.gtk.Private.UDisks2VolumeMonitor[1729]:
> index_parse.c:191: indx_parse(): error opening /run/media/angelo
> ================l
>
> I use the partitions on USB Hard Disk in order to do the back up of the
> data of the computer..
> And now I am looking for an alternative method (solution) to mounting the
> partitions..
>
> another thing I would like to ask :
> to use autofs for partitions on my USB HD that is permanently connected to
> computer,
> it is mandatory install also NFS (network file system)  ???
>
> Thank you
>
> Angelo
>
> On Fri, Jan 5, 2018 at 12:19 AM, Samuel Sieb  wrote:
> > On 12/27/2017 01:24 AM, Angelo Moreschini wrote:
> > > However, this solution for backing up the data is problematic, because
> > > _I always receive messages with the request of access to the partitions
> > > __of the “backup-partitions”__by "nautilus"_ - every time that I use the
> > > "find" command.
> >
> > I don't understand this.  Can you provide more details about what is
> > happening here?  I wonder if systemd is lazy mounting the drives, so they
> > don't actually mount until you access them for the first time.  If you look
> > in the journal, you should be able to tell by the timestamps when the drive
> > gets mounted.
> >
> > users mailing list -- [e-mail]
> > To unsubscribe send an email to [e-mail]

[Samuel Sieb]

On 01/05/2018 12:13 AM, Angelo Moreschini wrote:
> _here some line of command_ : _sudo journalctl  | grep -i 
> PRTZ_programming_*(PRTZ_programming = name of partition I made on USB HD)**
>
> Nov 12 09:29:50 localhost.pluto gnome-session[1798]: Gjs-Message: JS 
> LOG: Unable to mount volume PRTZ_programming: Gio.IOErrorEnum: Error 
> mounting system-managed device /dev/sdb2: Command-line `mount 
> "/media/BKx_programming"' exited with non-zero exit status 18: Failed to 
> write lock '/dev/sdb2': Resource temporarily unavailable
> Nov 12 09:29:55 localhost.pluto gnome-session[1798]: Gjs-Message: JS 
> LOG: Unable to mount volume PRTZ_programming: Gio.IOErrorEnum: Error 
> mounting system-managed device /dev/sdb2: Command-line `mount 
> "/media/BKx_programming"' exited with non-zero exit status 18: Failed to 
> write lock '/dev/sdb2': Resource temporarily unavailable

These lines are because Gnome sees a USB drive and tries to mount it, 
but finds out that it's being managed already.
> Nov 12 09:29:57 localhost.pluto ntfs-3g[5657]: Mounted /dev/sdb2 
> (Read-Write, label "PRTZ_programming", NTFS 3.1)
> Nov 12 09:31:08 localhost.pluto ntfs-3g[5657]: Unmounting /dev/sdb2 
> (PRTZ_programming)
> Nov 12 11:02:54 localhost.pluto ntfs-3g[691]: Mounted /dev/sdb2 
> (Read-Write, label "PRTZ_programming", NTFS 3.1)
> Nov 12 19:59:58 localhost.pluto ntfs-3g[691]: Unmounting /dev/sdb2 
> (PRTZ_programming)

I assume the mounting time is when you run your find command.  I have no 
idea what is unmounting it unless systemd is using something like autofs.
> Nov 20 10:33:09 localhost.pluto udisksd[1506]: Mounted /dev/sdb2 at 
> /run/media/angelo_dev/PRTZ_programming on behalf of uid 1003
> Nov 20 10:33:09 localhost.pluto 
> org.gtk.Private.UDisks2VolumeMonitor[1729]: index_parse.c:191: 
> indx_parse(): error opening /run/media/angelo

This time it looks like udisksd got it instead of whatever else was 
mounting it before.
> another thing I would like to ask :
> to use autofs for partitions on my USB HD that is permanently connected 
> to computer,
> it is mandatory install also NFS (network file system)  ???

You shouldn't have to.  NFS is only one thing (probably the most common 
one though) that is managed using autofs.

[Samuel Sieb]

On 01/05/2018 12:37 AM, Samuel Sieb wrote:
> On 01/05/2018 12:13 AM, Angelo Moreschini wrote:
> > Nov 12 11:02:54 localhost.pluto ntfs-3g[691]: Mounted /dev/sdb2 
> > (Read-Write, label "PRTZ_programming", NTFS 3.1)
> > Nov 12 19:59:58 localhost.pluto ntfs-3g[691]: Unmounting /dev/sdb2 
> > (PRTZ_programming)
>
> I assume the mounting time is when you run your find command.  I have no 
> idea what is unmounting it unless systemd is using something like autofs.

I forgot to mention that each time this gets mounted, Nautilus will be 
notified that a new device is available and so it will popup the 
notification for you.  If you can figure out what is unmounting the 
drive, you won't get the notifications any more.

[Angelo Moreschini]

I have problem to configure autofs, in order to use  the partitions that I
made on my USB HD - for backing up the data of the computer.

----------
*(I am thinking that, perhaps, the names to indicate the "mounting point"
and the "automounter map" are not the same that are used in sftab file <for
the fix mounting>).*

I found an article: (Automatically mount USB external drive with autofs -
https://linuxconfig.org/automatically-mount-usb-external-drive-with-autofs )
There the problem is seriously explained ... (differently than in other
articles there is explicitly considerate the mounting of an *USB HD*).
And there is suggested to use "udev" to create a "USB device base name
permanent" for the device... (and this look to me to be advisable).

But following this procedure the complexity of the problem is growing
exponentially (I need also install udev ?).
----------

So I would like ask some help, before to give up... :-).

What are the correct steps to do the automatically mounting of a HD in
order to use it for backing up data on USB Hard Disk ?

Thank you

Angelo

On Fri, Jan 5, 2018 at 10:40 AM, Samuel Sieb  wrote:
> On 01/05/2018 12:37 AM, Samuel Sieb wrote:
> > On 01/05/2018 12:13 AM, Angelo Moreschini wrote:
> > > Nov 12 11:02:54 localhost.pluto ntfs-3g[691]: Mounted /dev/sdb2
> > > (Read-Write, label "PRTZ_programming", NTFS 3.1)
> > > Nov 12 19:59:58 localhost.pluto ntfs-3g[691]: Unmounting /dev/sdb2
> > > (PRTZ_programming)
> >
> > I assume the mounting time is when you run your find command.  I have no
> > idea what is unmounting it unless systemd is using something like autofs.
>
> I forgot to mention that each time this gets mounted, Nautilus will be
> notified that a new device is available and so it will popup the
> notification for you.  If you can figure out what is unmounting the drive,
> you won't get the notifications any more.
>
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]

[stan]

On Sat, 6 Jan 2018 12:30:33 +0200
Angelo Moreschini  wrote:
> I have problem to configure autofs, in order to use  the partitions
> that I made on my USB HD - for backing up the data of the computer.
>
> *(I am thinking that, perhaps, the names to indicate the "mounting
> point" and the "automounter map" are not the same that are used in
> sftab file <for the fix mounting>).*
>
> I found an article: (Automatically mount USB external drive with
> autofs -
> https://linuxconfig.org/automatically-mount-usb-external-drive-with-autofs )
> There the problem is seriously explained ... (differently than in
> other articles there is explicitly considerate the mounting of an
> *USB HD*). And there is suggested to use "udev" to create a "USB
> device base name permanent" for the device... (and this look to me to
> be advisable).

I haven't done this, but from the article it seems that you have either
an entry in fstab and use mount -a to mount the drive after plugging it
in, or you follow the udev - autofs route without an entry in fstab.
> But following this procedure the complexity of the problem is growing
> exponentially (I need also install udev ?).

I think udev is part of the base fedora system, so you will already
have it installed, as part of package systemd-udev.

The recipe in the article doesn't seem that bad.  Basically three steps:
identify and specify the drive, let udev know about the drive, set up
autofs to mount the drive.

[Joe Zeff]

On 01/06/2018 09:40 AM, stan wrote:
> I haven't done this, but from the article it seems that you have either
> an entry in fstab and use mount -a to mount the drive after plugging it
> in, or you follow the udev - autofs route without an entry in fstab.

mount -a will mount everything in fstab.  Is that what you want?

[stan]

On Sat, 6 Jan 2018 10:50:14 -0800
Joe Zeff  wrote:
> On 01/06/2018 09:40 AM, stan wrote:
> > I haven't done this, but from the article it seems that you have
> > either an entry in fstab and use mount -a to mount the drive after
> > plugging it in, or you follow the udev - autofs route without an
> > entry in fstab.
>
> mount -a will mount everything in fstab.  Is that what you want?

Well, everything else should already be mounted since the system is up
and running when he plugs in the drive, so it will be a no-op for
everything except the USB drive he just plugged in.

[Angelo Moreschini]

Really, (after many tests) I cannot understand what the problem can be...
I disabled all auto mounting functions putting in comment all the rows of
the file auto.master
and after I checked the service autofs :

=================================
[angelo_dev@localhost ~]$ sudo systemctl status autofs -l
● autofs.service - Automounts filesystems on demand
   Loaded: loaded (/usr/lib/systemd/system/autofs.service; enabled)
   Active: *active (running)* since Sun 2018-01-07 09:01:06 IST; 1min 25s
ago
  Process: 1205 ExecStart=/usr/sbin/automount $OPTIONS --pid-file
/run/autofs.pid (code=exited, status=0/SUCCESS)
 Main PID: 1214 (automount)
   CGroup: /system.slice/autofs.service
           └─1214 /usr/sbin/automount --pid-file /run/autofs.pid

Jan 07 09:01:05 localhost.pluto automount[1214]:

* setautomntent: lookup(sss): setautomntent: No such file or
directory=================================*

*Independently of the set up That I made,  the service doesn't work
correctly...*
what can be the cause ?   What can I try still ?

regards

Angelo