Re: Data backup- (udev problem)

[Angelo Moreschini]

I  learned much today...


Thank you for your time,  as well the problem is not fixed, you have really
helped me.

good night

Angelo

On Sun, Jan 7, 2018 at 10:02 PM,  wrote:

>
> On Sun, 07 Jan 2018 21:37:51 +0200 Angelo Moreschini wrote:
>
> > So you say :  the directory exist.. although  I cannot see them ?
> > this look to be not much clear   (but really you are right :-). )...
>
> That's the way autofs works for such an indirect map by default. This
> may ne changed: see man auto.master, look for browse.
>
> > Jan 07 21:11:38 localhost.pluto automount[8301]: >> ntfs-3g: Unknown
> option '-s'.
>
> Try to suppress the ,defaults option in /etc/auto.master
>
> 
> /srv/   /etc/auto.ext-usb --timeout=10
> 
>
> then restart autofs, but that will fail also. See below.
>
> > [angelo_dev@localhost ~]$ * mount -v | grep /media*
> > /dev/sdb3 on /run/media/angelo_dev/PRTZ_data-personal type fuseblk
> > (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_
> permissions,allow_other,blksize=4096,uhelper=udisks2)
> ...
>
> This shows that Gnome is still mounting itself the partitions of this
> disk (using their labels).
>
> autofs will fail to mount those partitions if they are already
> mounted.
>
> Try to find how to setup Gnome to *not* mount them (I have no idea).
>
> --
> francis.montag...@inria.fr, SIC-SAM, Tel: (33) 04 92 38 79 11, Bur: C111
> INRIA Sophia, 2004, route des Lucioles - BP 93 06902 Sophia Antipolis Cedex
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
>
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Data backup- (udev problem)

[Francis . Montagnac]

On Sun, 07 Jan 2018 21:37:51 +0200 Angelo Moreschini wrote:

> So you say :  the directory exist.. although  I cannot see them ?
> this look to be not much clear   (but really you are right :-). )...

That's the way autofs works for such an indirect map by default. This
may ne changed: see man auto.master, look for browse.

> Jan 07 21:11:38 localhost.pluto automount[8301]: >> ntfs-3g: Unknown option 
> '-s'.

Try to suppress the ,defaults option in /etc/auto.master


/srv/   /etc/auto.ext-usb --timeout=10


then restart autofs, but that will fail also. See below.

> [angelo_dev@localhost ~]$ * mount -v | grep /media*
> /dev/sdb3 on /run/media/angelo_dev/PRTZ_data-personal type fuseblk
> (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096,uhelper=udisks2)
...

This shows that Gnome is still mounting itself the partitions of this
disk (using their labels).

autofs will fail to mount those partitions if they are already
mounted.

Try to find how to setup Gnome to *not* mount them (I have no idea).

-- 
francis.montag...@inria.fr, SIC-SAM, Tel: (33) 04 92 38 79 11, Bur: C111
INRIA Sophia, 2004, route des Lucioles - BP 93 06902 Sophia Antipolis Cedex
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Data backup- (udev problem)

[Angelo Moreschini]

the *umount failed ..*.  :

[angelo_dev@localhost ~]$  sudo umount /srv/BKx_data-personal
 umount: /srv/BKx_data-personal: mountpoint not found
[angelo_dev@localhost ~]$ sudo umount /srv/BKx_programming
  umount: /srv/BKx_programming: mountpoint not found
[angelo_dev@localhost ~]$sudo umount /srv/BKx_data-common
  umount: /srv/BKx_data-common: mountpoint not found


On Sun, Jan 7, 2018 at 9:37 PM, Angelo Moreschini  wrote:

> OK ... I understand... ...
>
>
> So you say :  the directory exist.. although  I cannot see them ?
> this look to be not much clear   (but really you are right :-). )...
>
>
> --  here the output you asked :
> [angelo_dev@localhost ~]$ sudo *journalctl --since 19:57:00 -u
> autofs.service*
> -- Logs begin at Mon 2015-06-22 08:17:25 IDT, end at Sun 2018-01-07
> 21:12:48 IST. --
> Jan 07 21:11:38 localhost.pluto automount[8301]: attempting to mount entry
> /srv/BKx_programming
> Jan 07 21:11:38 localhost.pluto automount[8301]: >> ntfs-3g: Unknown
> option '-s'.
> Jan 07 21:11:38 localhost.pluto automount[8301]: >> ntfs-3g 2014.2.15
> integrated FUSE 27 - Third Generatio
> Jan 07 21:11:38 localhost.pluto automount[8301]: >>
> Configuration type 1, XATTRS are on, P
> Jan 07 21:11:38 localhost.pluto automount[8301]: >> Copyright (C)
> 2005-2007 Yura Pakhuchiy
> Jan 07 21:11:38 localhost.pluto automount[8301]: >> Copyright (C)
> 2006-2009 Szabolcs Szakacsits
> Jan 07 21:11:38 localhost.pluto automount[8301]: >> Copyright (C)
> 2007-2012 Jean-Pierre Andre
> Jan 07 21:11:38 localhost.pluto automount[8301]: >> Copyright (C) 2009
> Erik Larsson
> Jan 07 21:11:38 localhost.pluto automount[8301]: >> Usage:ntfs-3g [-o
> option[,...]]  Jan 07 21:11:38 localhost.pluto automount[8301]: >> Options:  ro
> (read-only mount), windows_names, uid=, g
> Jan 07 21:11:38 localhost.pluto automount[8301]: >>   umask=,
> fmask=, dmask=, streams_interface=.
> Jan 07 21:11:38 localhost.pluto automount[8301]: >>   Please see
> the details in the manual (type:
> Jan 07 21:11:38 localhost.pluto automount[8301]: >> Example: ntfs-3g
> /dev/sda1 /mnt/windows
> Jan 07 21:11:38 localhost.pluto automount[8301]: >> News, support and
> information:  http://tuxera.com
> Jan 07 21:11:38 localhost.pluto automount[8301]: mount(generic): failed to
> mount /dev/disk/by-uuid/479F99A
> Jan 07 21:11:38 localhost.pluto automount[8301]: *failed to mount
> /srv/BKx_programming   **=---> *what the reason ?
> --
> [angelo_dev@localhost ~]$ *ps auxw | grep automount*
> root  8301  0.0  0.0 329752  4764 ?Ssl  19:51   0:01
> /usr/sbin/automount -v --pid-file /run/autofs.pid
> angelo_+ 11937  0.0  0.0 112996  2252 pts/1S+   21:15   0:00 grep
> --color=auto automount
>
> ---
> [angelo_dev@localhost ~]$  *systemctl cat autofs.service*
> # /usr/lib/systemd/system/autofs.service
> [Unit]
> Description=Automounts filesystems on demand
> After=network.target ypbind.service sssd.service network-online.target
> Wants=network-online.target
>
> [Service]
> Type=forking
> PIDFile=/run/autofs.pid
> EnvironmentFile=-/etc/sysconfig/autofs
> ExecStart=/usr/sbin/automount $OPTIONS --pid-file /run/autofs.pid
> ExecReload=/usr/bin/kill -HUP $MAINPID
> TimeoutSec=180
>
> [Install]
> WantedBy=multi-user.target
>
> 
> [angelo_dev@localhost ~]$ * mount -v | grep /media*
> /dev/sdb3 on /run/media/angelo_dev/PRTZ_data-personal type fuseblk
> (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_
> permissions,allow_other,blksize=4096,uhelper=udisks2)
> /dev/sdb1 on /run/media/angelo_dev/PRTZ_data-common type fuseblk
> (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_
> permissions,allow_other,blksize=4096,uhelper=udisks2)
> /dev/sdb2 on /run/media/angelo_dev/PRTZ_programming type fuseblk
> (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_
> permissions,allow_other,blksize=4096,uhelper=udisks2)
>
> --
> [angelo_dev@localhost ~]$* mount -v | grep BK*
> [angelo_dev@localhost ~]$
> (nothing... - no output)
>
> ---
> perhaps I have to buy another USB HD ??
> The actual can be defective (this can be right -there are some block not
> right..)
>
>
>
>
>
>
> On Sun, Jan 7, 2018 at 9:06 PM,  wrote:
>
>>
>> On Sun, 07 Jan 2018 20:52:39 +0200 Angelo Moreschini wrote:
>>
>> > perhaps the /srv directory is a special one ? Also administrator cannot
>> > make directory inside it ?
>>
>> Yes and no: it is a mountpoint directory managed exclusively by autofs
>> (since with ssetup auto.master for that).
>>
>> This is normal to not be able to create sub-directories under /srv.
>>
>> Please read carefully what I said earlier:
>>
>>   Note also that "ls /srv" will show nothing, but "ls
>> /srv/BKx_programming"
>>   will do the (auto)mount and show you the content.
>>
>> And what about:
>>
>>   You are running journalctl as you. Except if your are in the wheel
>>   group (or some other ones) you will 

Re: Data backup- (udev problem)

[Angelo Moreschini]

OK ... I understand... ...


So you say :  the directory exist.. although  I cannot see them ?
this look to be not much clear   (but really you are right :-). )...


--  here the output you asked :
[angelo_dev@localhost ~]$ sudo *journalctl --since 19:57:00 -u
autofs.service*
-- Logs begin at Mon 2015-06-22 08:17:25 IDT, end at Sun 2018-01-07
21:12:48 IST. --
Jan 07 21:11:38 localhost.pluto automount[8301]: attempting to mount entry
/srv/BKx_programming
Jan 07 21:11:38 localhost.pluto automount[8301]: >> ntfs-3g: Unknown option
'-s'.
Jan 07 21:11:38 localhost.pluto automount[8301]: >> ntfs-3g 2014.2.15
integrated FUSE 27 - Third Generatio
Jan 07 21:11:38 localhost.pluto automount[8301]: >>
Configuration type 1, XATTRS are on, P
Jan 07 21:11:38 localhost.pluto automount[8301]: >> Copyright (C) 2005-2007
Yura Pakhuchiy
Jan 07 21:11:38 localhost.pluto automount[8301]: >> Copyright (C) 2006-2009
Szabolcs Szakacsits
Jan 07 21:11:38 localhost.pluto automount[8301]: >> Copyright (C) 2007-2012
Jean-Pierre Andre
Jan 07 21:11:38 localhost.pluto automount[8301]: >> Copyright (C) 2009 Erik
Larsson
Jan 07 21:11:38 localhost.pluto automount[8301]: >> Usage:ntfs-3g [-o
option[,...]] > Options:  ro (read-only
mount), windows_names, uid=, g
Jan 07 21:11:38 localhost.pluto automount[8301]: >>   umask=,
fmask=, dmask=, streams_interface=.
Jan 07 21:11:38 localhost.pluto automount[8301]: >>   Please see
the details in the manual (type:
Jan 07 21:11:38 localhost.pluto automount[8301]: >> Example: ntfs-3g
/dev/sda1 /mnt/windows
Jan 07 21:11:38 localhost.pluto automount[8301]: >> News, support and
information:  http://tuxera.com
Jan 07 21:11:38 localhost.pluto automount[8301]: mount(generic): failed to
mount /dev/disk/by-uuid/479F99A
Jan 07 21:11:38 localhost.pluto automount[8301]: *failed to mount
/srv/BKx_programming   **=---> *what the reason ?
--
[angelo_dev@localhost ~]$ *ps auxw | grep automount*
root  8301  0.0  0.0 329752  4764 ?Ssl  19:51   0:01
/usr/sbin/automount -v --pid-file /run/autofs.pid
angelo_+ 11937  0.0  0.0 112996  2252 pts/1S+   21:15   0:00 grep
--color=auto automount

---
[angelo_dev@localhost ~]$  *systemctl cat autofs.service*
# /usr/lib/systemd/system/autofs.service
[Unit]
Description=Automounts filesystems on demand
After=network.target ypbind.service sssd.service network-online.target
Wants=network-online.target

[Service]
Type=forking
PIDFile=/run/autofs.pid
EnvironmentFile=-/etc/sysconfig/autofs
ExecStart=/usr/sbin/automount $OPTIONS --pid-file /run/autofs.pid
ExecReload=/usr/bin/kill -HUP $MAINPID
TimeoutSec=180

[Install]
WantedBy=multi-user.target


[angelo_dev@localhost ~]$ * mount -v | grep /media*
/dev/sdb3 on /run/media/angelo_dev/PRTZ_data-personal type fuseblk
(rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096,uhelper=udisks2)
/dev/sdb1 on /run/media/angelo_dev/PRTZ_data-common type fuseblk
(rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096,uhelper=udisks2)
/dev/sdb2 on /run/media/angelo_dev/PRTZ_programming type fuseblk
(rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096,uhelper=udisks2)

--
[angelo_dev@localhost ~]$* mount -v | grep BK*
[angelo_dev@localhost ~]$
(nothing... - no output)

---
perhaps I have to buy another USB HD ??
The actual can be defective (this can be right -there are some block not
right..)






On Sun, Jan 7, 2018 at 9:06 PM,  wrote:

>
> On Sun, 07 Jan 2018 20:52:39 +0200 Angelo Moreschini wrote:
>
> > perhaps the /srv directory is a special one ? Also administrator cannot
> > make directory inside it ?
>
> Yes and no: it is a mountpoint directory managed exclusively by autofs
> (since with ssetup auto.master for that).
>
> This is normal to not be able to create sub-directories under /srv.
>
> Please read carefully what I said earlier:
>
>   Note also that "ls /srv" will show nothing, but "ls /srv/BKx_programming"
>   will do the (auto)mount and show you the content.
>
> And what about:
>
>   You are running journalctl as you. Except if your are in the wheel
>   group (or some other ones) you will not see the system journal.
>
>   What gives the following commands:
>
> sudo journalctl --since 19:57:00 -u autofs.service
>
> ps auxw | grep automount
>
> systemctl cat autofs.service
>
> mount -v | grep /media
>
> mount -v | grep BK
>
>   You should also manually umount every BK directories under /media:
>
>sudo umount /srv/BKx_data-personal
>sudo umount /srv/BKx_programming
>sudo umount /srv/BKx_data-common
>
>
> --
> francis.montag...@inria.fr, SIC-SAM, Tel: (33) 04 92 38 79 11, Bur: C111
> INRIA Sophia, 2004, route des Lucioles - BP 93 06902 Sophia Antipolis Cedex
> ___
> users mailing list -- 

Re: Data backup- (udev problem)

[Bob Marcan]

On Sun, 7 Jan 2018 20:44:57 +0200
Angelo Moreschini  wrote:

> wait ...  I checked better  and I saw the directories doesn't exits in
> /srv...
> 
> trying to create now but I didn't have success.. :
> 
> [angelo_dev@localhost srv]$ sudo mkdir BKx_programming
> 
> 
> *mkdir: cannot create directory ‘BKx_programming’: Permission denied*
> that is funny ... How it can be ? I used  privileges of SU..
> 

In /etc/auto.master,
 ghost will create and remove directory on demand:
...
/media  /etc/auto.master.d/auto.media --timeout=60 --ghost
...

/etc/auto.master.d/auto.media:
...
dvd -fstype=iso9660,ro,nosuid,nodev :/dev/sr0
WD160-Canyon-fstype=auto,noatime,nodiratime 
:/dev/disk/by-label/WD160-Canyon
WD500-SunBright -fstype=auto,noatime,nodiratime 
:/dev/disk/by-label/WD500-SunBright
WD500-MyBook-fstype=auto,noatime,nodiratime 
:/dev/disk/by-label/WD500-MyBook
USB-vfat-fstype=vfat,noatime,nodiratime,uid=1000,gid=1000   
:/dev/disk/by-label/USB-vfat
USB-ext2-fstype=ext2,noatime,nodiratime 
:/dev/disk/by-label/USB-ext2
...

Do not forget to reload autofs.
BR, Bob





___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Data backup- (udev problem)

[Francis . Montagnac]

On Sun, 07 Jan 2018 20:52:39 +0200 Angelo Moreschini wrote:

> perhaps the /srv directory is a special one ? Also administrator cannot
> make directory inside it ?

Yes and no: it is a mountpoint directory managed exclusively by autofs
(since with ssetup auto.master for that).

This is normal to not be able to create sub-directories under /srv.

Please read carefully what I said earlier:

  Note also that "ls /srv" will show nothing, but "ls /srv/BKx_programming"
  will do the (auto)mount and show you the content.

And what about:

  You are running journalctl as you. Except if your are in the wheel
  group (or some other ones) you will not see the system journal.

  What gives the following commands:

sudo journalctl --since 19:57:00 -u autofs.service

ps auxw | grep automount

systemctl cat autofs.service

mount -v | grep /media

mount -v | grep BK

  You should also manually umount every BK directories under /media:

   sudo umount /srv/BKx_data-personal
   sudo umount /srv/BKx_programming 
   sudo umount /srv/BKx_data-common


-- 
francis.montag...@inria.fr, SIC-SAM, Tel: (33) 04 92 38 79 11, Bur: C111
INRIA Sophia, 2004, route des Lucioles - BP 93 06902 Sophia Antipolis Cedex
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Data backup- (udev problem)

[Angelo Moreschini]

we have to use another directory than /srv .
The directories for mounting partitions weren't created there ...,and look
it is not possible to create there ...

On Sun, Jan 7, 2018 at 8:52 PM, Angelo Moreschini  wrote:

> perhaps the /srv directory is a special one ? Also administrator cannot
> make directory inside it ?
>
> On Sun, Jan 7, 2018 at 8:44 PM, Angelo Moreschini <
> mrangelo.fed...@gmail.com> wrote:
>
>> wait ...  I checked better  and I saw the directories doesn't exits in
>> /srv...
>>
>> trying to create now but I didn't have success.. :
>>
>> [angelo_dev@localhost srv]$ sudo mkdir BKx_programming
>>
>>
>> *mkdir: cannot create directory ‘BKx_programming’: Permission denied*
>> that is funny ... How it can be ? I used  privileges of SU..
>>
>> On Sun, Jan 7, 2018 at 8:17 PM, stan 
>> wrote:
>>
>>> On Sun, 7 Jan 2018 17:58:07 +0200
>>> Angelo Moreschini  wrote:
>>>
>>> > Hi Francis,
>>> >
>>> > I followed your procedure,
>>> >
>>> > I can see the partitions by nautilus as is the standard, but still I
>>> > cannot see them from the command line ..:
>>> > 
>>> > [angelo_dev@localhost ~]$ ls /srv/BKx_programming
>>> > ls: cannot access /srv/BKx_programming: *No such file or directory*
>>> > 
>>> > (the output about the service is :)
>>> > ---
>>> > [angelo_dev@localhost ~]$ sudo systemctl status autofs
>>> > [sudo] password for angelo_dev:
>>> > ● autofs.service - Automounts filesystems on demand
>>> >Loaded: loaded (/usr/lib/systemd/system/autofs.service; enabled)
>>> >Active: active (running) since Sun 2018-01-07 17:36:34 IST; 16min
>>> > ago Process: 1202 ExecStart=/usr/sbin/automount $OPTIONS --pid-file
>>> > /run/autofs.pid (code=exited, status=0/SUCCESS)
>>> >  Main PID: 1220 (automount)
>>> >CGroup: /system.slice/autofs.service
>>> >└─1220 /usr/sbin/automount --pid-file /run/autofs.pid
>>> > =
>>> >
>>> > what to say ??
>>>
>>> From the article you linked.  Perhaps this is the reason you don't see
>>> them from the command line.
>>> """
>>> Please note, although our drive is now listed as an active mount point
>>> the disk is not mounted yet! autofs only waits for user to access
>>> specified mount point directory and once that happens it will mount the
>>> filesystem.
>>>
>>> Example:
>>>
>>> $ cd /media/
>>> $ ls
>>> $ cd Iomega
>>> $ ls
>>> lost.dir  music  picture  ps3  video mystuff
>>> $ cd ..
>>> $ ls
>>> Iomega
>>>
>>> From the output above you can see that Iomega directory was created
>>> only when I tried to access it. Every time you now plug in you USB
>>> external disk you can instantly access it via some sort of Desktop or
>>> Bookmark shortcut. I hope this helps !
>>> """
>>>
>>> Try doing a cd into the directory, and then doing an ls.
>>> ___
>>> users mailing list -- users@lists.fedoraproject.org
>>> To unsubscribe send an email to users-le...@lists.fedoraproject.org
>>>
>>
>>
>
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Data backup- (udev problem)

[Angelo Moreschini]

perhaps the /srv directory is a special one ? Also administrator cannot
make directory inside it ?

On Sun, Jan 7, 2018 at 8:44 PM, Angelo Moreschini  wrote:

> wait ...  I checked better  and I saw the directories doesn't exits in
> /srv...
>
> trying to create now but I didn't have success.. :
>
> [angelo_dev@localhost srv]$ sudo mkdir BKx_programming
>
>
> *mkdir: cannot create directory ‘BKx_programming’: Permission denied*
> that is funny ... How it can be ? I used  privileges of SU..
>
> On Sun, Jan 7, 2018 at 8:17 PM, stan  wrote:
>
>> On Sun, 7 Jan 2018 17:58:07 +0200
>> Angelo Moreschini  wrote:
>>
>> > Hi Francis,
>> >
>> > I followed your procedure,
>> >
>> > I can see the partitions by nautilus as is the standard, but still I
>> > cannot see them from the command line ..:
>> > 
>> > [angelo_dev@localhost ~]$ ls /srv/BKx_programming
>> > ls: cannot access /srv/BKx_programming: *No such file or directory*
>> > 
>> > (the output about the service is :)
>> > ---
>> > [angelo_dev@localhost ~]$ sudo systemctl status autofs
>> > [sudo] password for angelo_dev:
>> > ● autofs.service - Automounts filesystems on demand
>> >Loaded: loaded (/usr/lib/systemd/system/autofs.service; enabled)
>> >Active: active (running) since Sun 2018-01-07 17:36:34 IST; 16min
>> > ago Process: 1202 ExecStart=/usr/sbin/automount $OPTIONS --pid-file
>> > /run/autofs.pid (code=exited, status=0/SUCCESS)
>> >  Main PID: 1220 (automount)
>> >CGroup: /system.slice/autofs.service
>> >└─1220 /usr/sbin/automount --pid-file /run/autofs.pid
>> > =
>> >
>> > what to say ??
>>
>> From the article you linked.  Perhaps this is the reason you don't see
>> them from the command line.
>> """
>> Please note, although our drive is now listed as an active mount point
>> the disk is not mounted yet! autofs only waits for user to access
>> specified mount point directory and once that happens it will mount the
>> filesystem.
>>
>> Example:
>>
>> $ cd /media/
>> $ ls
>> $ cd Iomega
>> $ ls
>> lost.dir  music  picture  ps3  video mystuff
>> $ cd ..
>> $ ls
>> Iomega
>>
>> From the output above you can see that Iomega directory was created
>> only when I tried to access it. Every time you now plug in you USB
>> external disk you can instantly access it via some sort of Desktop or
>> Bookmark shortcut. I hope this helps !
>> """
>>
>> Try doing a cd into the directory, and then doing an ls.
>> ___
>> users mailing list -- users@lists.fedoraproject.org
>> To unsubscribe send an email to users-le...@lists.fedoraproject.org
>>
>
>
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Data backup- (udev problem)

[Angelo Moreschini]

wait ...  I checked better  and I saw the directories doesn't exits in
/srv...

trying to create now but I didn't have success.. :

[angelo_dev@localhost srv]$ sudo mkdir BKx_programming


*mkdir: cannot create directory ‘BKx_programming’: Permission denied*
that is funny ... How it can be ? I used  privileges of SU..

On Sun, Jan 7, 2018 at 8:17 PM, stan  wrote:

> On Sun, 7 Jan 2018 17:58:07 +0200
> Angelo Moreschini  wrote:
>
> > Hi Francis,
> >
> > I followed your procedure,
> >
> > I can see the partitions by nautilus as is the standard, but still I
> > cannot see them from the command line ..:
> > 
> > [angelo_dev@localhost ~]$ ls /srv/BKx_programming
> > ls: cannot access /srv/BKx_programming: *No such file or directory*
> > 
> > (the output about the service is :)
> > ---
> > [angelo_dev@localhost ~]$ sudo systemctl status autofs
> > [sudo] password for angelo_dev:
> > ● autofs.service - Automounts filesystems on demand
> >Loaded: loaded (/usr/lib/systemd/system/autofs.service; enabled)
> >Active: active (running) since Sun 2018-01-07 17:36:34 IST; 16min
> > ago Process: 1202 ExecStart=/usr/sbin/automount $OPTIONS --pid-file
> > /run/autofs.pid (code=exited, status=0/SUCCESS)
> >  Main PID: 1220 (automount)
> >CGroup: /system.slice/autofs.service
> >└─1220 /usr/sbin/automount --pid-file /run/autofs.pid
> > =
> >
> > what to say ??
>
> From the article you linked.  Perhaps this is the reason you don't see
> them from the command line.
> """
> Please note, although our drive is now listed as an active mount point
> the disk is not mounted yet! autofs only waits for user to access
> specified mount point directory and once that happens it will mount the
> filesystem.
>
> Example:
>
> $ cd /media/
> $ ls
> $ cd Iomega
> $ ls
> lost.dir  music  picture  ps3  video mystuff
> $ cd ..
> $ ls
> Iomega
>
> From the output above you can see that Iomega directory was created
> only when I tried to access it. Every time you now plug in you USB
> external disk you can instantly access it via some sort of Desktop or
> Bookmark shortcut. I hope this helps !
> """
>
> Try doing a cd into the directory, and then doing an ls.
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
>
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Data backup- (udev problem)

[Francis . Montagnac]

On Sun, 07 Jan 2018 20:01:18 +0200 Angelo Moreschini wrote:

> I set OPTIONS="-v" in /etc/sysconfig/autofs:
> I restart the autofs service

> and after tried again to look for the mounted partition:

> [angelo_dev@localhost ~]$ ls /srv/BKx_programming
> ls: cannot access /srv/BKx_programming: *No such file or directory*

> * still noting to do *

> *also the output of journalclt is still null.. *:

This is abnormal. You should see:

systemd[1]: Starting Automounts filesystems on demand...
automount[...]: Starting automounter version .., master map /etc/auto.master
...

> [angelo_dev@localhost ~]$ journalctl --since 19:57:00 -u autofs.service
> *-- Logs begin at Thu 2016-12-29 08:03:30 IST, end at Sun 2018-01-07
> 19:57:31 IST. --*

You are running journalctl as you. Except if your are in the wheel
group (or some other ones) you will not see the system journal.

What gives the following commands:

  sudo journalctl --since 19:57:00 -u autofs.service

  ps auxw | grep automount

  systemctl cat autofs.service

  mount -v | grep /media

  mount -v | grep BK

You should also manually umount every BK directories under /media:

 sudo umount /srv/BKx_data-personal
 sudo umount /srv/BKx_programming 
 sudo umount /srv/BKx_data-common

-- 
francis
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Data backup- (udev problem)

[stan]

On Sun, 7 Jan 2018 17:58:07 +0200
Angelo Moreschini  wrote:

> Hi Francis,
> 
> I followed your procedure,
> 
> I can see the partitions by nautilus as is the standard, but still I
> cannot see them from the command line ..:
> 
> [angelo_dev@localhost ~]$ ls /srv/BKx_programming
> ls: cannot access /srv/BKx_programming: *No such file or directory*
> 
> (the output about the service is :)
> ---
> [angelo_dev@localhost ~]$ sudo systemctl status autofs
> [sudo] password for angelo_dev:
> ● autofs.service - Automounts filesystems on demand
>Loaded: loaded (/usr/lib/systemd/system/autofs.service; enabled)
>Active: active (running) since Sun 2018-01-07 17:36:34 IST; 16min
> ago Process: 1202 ExecStart=/usr/sbin/automount $OPTIONS --pid-file
> /run/autofs.pid (code=exited, status=0/SUCCESS)
>  Main PID: 1220 (automount)
>CGroup: /system.slice/autofs.service
>└─1220 /usr/sbin/automount --pid-file /run/autofs.pid
> =
> 
> what to say ??

From the article you linked.  Perhaps this is the reason you don't see
them from the command line.
"""
Please note, although our drive is now listed as an active mount point
the disk is not mounted yet! autofs only waits for user to access
specified mount point directory and once that happens it will mount the
filesystem.

Example:

$ cd /media/
$ ls
$ cd Iomega
$ ls
lost.dir  music  picture  ps3  video mystuff
$ cd ..
$ ls
Iomega

From the output above you can see that Iomega directory was created
only when I tried to access it. Every time you now plug in you USB
external disk you can instantly access it via some sort of Desktop or
Bookmark shortcut. I hope this helps !
"""

Try doing a cd into the directory, and then doing an ls.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Data backup- (udev problem)

[Angelo Moreschini]

I didn't removed the directories in /media..
but *surly no one row about the mounting of the partition is now in fstab.*

On Sun, Jan 7, 2018 at 8:09 PM, Angelo Moreschini  wrote:

> reading the documentation, I remember that I red that are some rules to
> write the auto.xxx files
> (like terminate the rows with "at the head" (crl)) but I didn't pay so
> much attention and now don't remember these exactly.
>
> Perhaps the problem is there ?
>
> On Sun, Jan 7, 2018 at 8:01 PM, Angelo Moreschini <
> mrangelo.fed...@gmail.com> wrote:
>
>> I set OPTIONS="-v" in /etc/sysconfig/autofs:
>> I restart the autofs service
>>
>> and after tried again to look for the mounted partition:
>>
>> [angelo_dev@localhost ~]$ ls /srv/BKx_programming
>> ls: cannot access /srv/BKx_programming: *No such file or directory*
>>
>> * still noting to do *
>>
>> *also the output of journalclt is still null.. *:
>> [angelo_dev@localhost ~]$ journalctl --since 19:57:00 -u autofs.service
>> *-- Logs begin at Thu 2016-12-29 08:03:30 IST, end at Sun 2018-01-07
>> 19:57:31 IST. --*
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> [angelo_dev@localhost ~]$ ls /srv/BKx_programming
>> ls: cannot access /srv/BKx_programming: No such file or directory
>>
>> On Sun, Jan 7, 2018 at 7:08 PM,  wrote:
>>
>>>
>>> On Sun, 07 Jan 2018 18:38:31 +0200 Angelo Moreschini wrote:
>>>
>>> > == auto.master -
>>> > /srv/   /etc/auto.ext-usb --timeout=10,defaults
>>> > == auto.ext-usb
>>> > BKx_programming   -fstype=ntfs   :/dev/disk/by-uuid/479F99A324FF4D1D
>>> > BKx_data-common   -fstype=ntfs   :/dev/disk/by-uuid/EA8266EA8266BB29
>>> > ===
>>>
>>> Ok.
>>>
>>> > *no output in journalctl  :*
>>> > [angelo_dev@localhost ~]$* journalctl --since 17:36:00 -u
>>> autofs.service*
>>> > -- Logs begin at Thu 2016-12-29 08:03:30 IST, end at Sun 2018-01-07
>>> > 18:29:19 IST. --
>>> > ---
>>>
>>> Try to put autofs in verbose mode. In /etc/sysconfig/autofs:
>>>
>>> OPTIONS="-v"
>>>
>>> then restart autofs.
>>>
>>> > *Jan 05 07:46:15* localhost.pluto gnome-session[1840]:
>>>
>>> Gnome (nautilus) is still trying to do the mount, and under /media.
>>>
>>> > ... Command-line `mount "/media/BKx_programming"'
>>> > exited with  non-zero exit
>>>
>>> This seems to show that the mounts of /media/BK... are still present
>>> in /etc/fstab.
>>>
>>> It it is really the case: umount all the /media/BK... and comment
>>> those mounts in /etc/fstab
>>>
>>> Note also that "ls /srv" will show nothing, but "ls /srv/BKx_programming"
>>> will do the (auto)mount and show you the content.
>>>
>>> --
>>> francis
>>> ___
>>> users mailing list -- users@lists.fedoraproject.org
>>> To unsubscribe send an email to users-le...@lists.fedoraproject.org
>>>
>>
>>
>
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Data backup- (udev problem)

[Angelo Moreschini]

reading the documentation, I remember that I red that are some rules to
write the auto.xxx files
(like terminate the rows with "at the head" (crl)) but I didn't pay so much
attention and now don't remember these exactly.

Perhaps the problem is there ?

On Sun, Jan 7, 2018 at 8:01 PM, Angelo Moreschini  wrote:

> I set OPTIONS="-v" in /etc/sysconfig/autofs:
> I restart the autofs service
>
> and after tried again to look for the mounted partition:
>
> [angelo_dev@localhost ~]$ ls /srv/BKx_programming
> ls: cannot access /srv/BKx_programming: *No such file or directory*
>
> * still noting to do *
>
> *also the output of journalclt is still null.. *:
> [angelo_dev@localhost ~]$ journalctl --since 19:57:00 -u autofs.service
> *-- Logs begin at Thu 2016-12-29 08:03:30 IST, end at Sun 2018-01-07
> 19:57:31 IST. --*
>
>
>
>
>
>
>
>
>
> [angelo_dev@localhost ~]$ ls /srv/BKx_programming
> ls: cannot access /srv/BKx_programming: No such file or directory
>
> On Sun, Jan 7, 2018 at 7:08 PM,  wrote:
>
>>
>> On Sun, 07 Jan 2018 18:38:31 +0200 Angelo Moreschini wrote:
>>
>> > == auto.master -
>> > /srv/   /etc/auto.ext-usb --timeout=10,defaults
>> > == auto.ext-usb
>> > BKx_programming   -fstype=ntfs   :/dev/disk/by-uuid/479F99A324FF4D1D
>> > BKx_data-common   -fstype=ntfs   :/dev/disk/by-uuid/EA8266EA8266BB29
>> > ===
>>
>> Ok.
>>
>> > *no output in journalctl  :*
>> > [angelo_dev@localhost ~]$* journalctl --since 17:36:00 -u
>> autofs.service*
>> > -- Logs begin at Thu 2016-12-29 08:03:30 IST, end at Sun 2018-01-07
>> > 18:29:19 IST. --
>> > ---
>>
>> Try to put autofs in verbose mode. In /etc/sysconfig/autofs:
>>
>> OPTIONS="-v"
>>
>> then restart autofs.
>>
>> > *Jan 05 07:46:15* localhost.pluto gnome-session[1840]:
>>
>> Gnome (nautilus) is still trying to do the mount, and under /media.
>>
>> > ... Command-line `mount "/media/BKx_programming"'
>> > exited with  non-zero exit
>>
>> This seems to show that the mounts of /media/BK... are still present
>> in /etc/fstab.
>>
>> It it is really the case: umount all the /media/BK... and comment
>> those mounts in /etc/fstab
>>
>> Note also that "ls /srv" will show nothing, but "ls /srv/BKx_programming"
>> will do the (auto)mount and show you the content.
>>
>> --
>> francis
>> ___
>> users mailing list -- users@lists.fedoraproject.org
>> To unsubscribe send an email to users-le...@lists.fedoraproject.org
>>
>
>
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Data backup- (udev problem)

[Angelo Moreschini]

I set OPTIONS="-v" in /etc/sysconfig/autofs:
I restart the autofs service

and after tried again to look for the mounted partition:

[angelo_dev@localhost ~]$ ls /srv/BKx_programming
ls: cannot access /srv/BKx_programming: *No such file or directory*

* still noting to do *

*also the output of journalclt is still null.. *:
[angelo_dev@localhost ~]$ journalctl --since 19:57:00 -u autofs.service
*-- Logs begin at Thu 2016-12-29 08:03:30 IST, end at Sun 2018-01-07
19:57:31 IST. --*









[angelo_dev@localhost ~]$ ls /srv/BKx_programming
ls: cannot access /srv/BKx_programming: No such file or directory

On Sun, Jan 7, 2018 at 7:08 PM,  wrote:

>
> On Sun, 07 Jan 2018 18:38:31 +0200 Angelo Moreschini wrote:
>
> > == auto.master -
> > /srv/   /etc/auto.ext-usb --timeout=10,defaults
> > == auto.ext-usb
> > BKx_programming   -fstype=ntfs   :/dev/disk/by-uuid/479F99A324FF4D1D
> > BKx_data-common   -fstype=ntfs   :/dev/disk/by-uuid/EA8266EA8266BB29
> > ===
>
> Ok.
>
> > *no output in journalctl  :*
> > [angelo_dev@localhost ~]$* journalctl --since 17:36:00 -u
> autofs.service*
> > -- Logs begin at Thu 2016-12-29 08:03:30 IST, end at Sun 2018-01-07
> > 18:29:19 IST. --
> > ---
>
> Try to put autofs in verbose mode. In /etc/sysconfig/autofs:
>
> OPTIONS="-v"
>
> then restart autofs.
>
> > *Jan 05 07:46:15* localhost.pluto gnome-session[1840]:
>
> Gnome (nautilus) is still trying to do the mount, and under /media.
>
> > ... Command-line `mount "/media/BKx_programming"'
> > exited with  non-zero exit
>
> This seems to show that the mounts of /media/BK... are still present
> in /etc/fstab.
>
> It it is really the case: umount all the /media/BK... and comment
> those mounts in /etc/fstab
>
> Note also that "ls /srv" will show nothing, but "ls /srv/BKx_programming"
> will do the (auto)mount and show you the content.
>
> --
> francis
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
>
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Data backup- (udev problem)

[Francis . Montagnac]

On Sun, 07 Jan 2018 18:38:31 +0200 Angelo Moreschini wrote:

> == auto.master -
> /srv/   /etc/auto.ext-usb --timeout=10,defaults
> == auto.ext-usb
> BKx_programming   -fstype=ntfs   :/dev/disk/by-uuid/479F99A324FF4D1D
> BKx_data-common   -fstype=ntfs   :/dev/disk/by-uuid/EA8266EA8266BB29
> ===

Ok.

> *no output in journalctl  :*
> [angelo_dev@localhost ~]$* journalctl --since 17:36:00 -u autofs.service*
> -- Logs begin at Thu 2016-12-29 08:03:30 IST, end at Sun 2018-01-07
> 18:29:19 IST. --
> ---

Try to put autofs in verbose mode. In /etc/sysconfig/autofs:

OPTIONS="-v"

then restart autofs.

> *Jan 05 07:46:15* localhost.pluto gnome-session[1840]:

Gnome (nautilus) is still trying to do the mount, and under /media.

> ... Command-line `mount "/media/BKx_programming"'
> exited with  non-zero exit
  
This seems to show that the mounts of /media/BK... are still present
in /etc/fstab.

It it is really the case: umount all the /media/BK... and comment
those mounts in /etc/fstab

Note also that "ls /srv" will show nothing, but "ls /srv/BKx_programming"
will do the (auto)mount and show you the content.

-- 
francis
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Data backup- (udev problem)

[Angelo Moreschini]

of curse I changed ... :

== auto.master -
/srv/   /etc/auto.ext-usb --timeout=10,defaults
== auto.ext-usb
BKx_programming   -fstype=ntfs   :/dev/disk/by-uuid/479F99A324FF4D1D
BKx_data-common   -fstype=ntfs   :/dev/disk/by-uuid/EA8266EA8266BB29
===
===

*no output in journalctl  :*
[angelo_dev@localhost ~]$* journalctl --since 17:36:00 -u autofs.service*
-- Logs begin at Thu 2016-12-29 08:03:30 IST, end at Sun 2018-01-07
18:29:19 IST. --
---
*this is the output for :  (the fes
last rows)*
*Jan 05 07:46:15* localhost.pluto gnome-session[1840]: 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

*Jan 05 07:46:18* localhost.pluto gnome-session[1840]: 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

*Jan 05 07:46:19* localhost.pluto
org.gtk.Private.UDisks2VolumeMonitor[1848]: index_parse.c:191:
indx_parse(): error opening /media/BKx_programming/BDMV/index.bdmv

*Jan 05 07:46:19* localhost.pluto
org.gtk.Private.UDisks2VolumeMonitor[1848]: index_parse.c:191:
indx_parse(): error opening /media/BKx_programming/BDMV/BACKUP/index.bdmv


On Sun, Jan 7, 2018 at 6:19 PM,  wrote:

>
> On Sun, 07 Jan 2018 17:58:07 +0200 Angelo Moreschini wrote:
>
> > I can see the partitions by nautilus as is the standard, but still I
> cannot
> > see them from the command line ..:
> > 
> > [angelo_dev@localhost ~]$ ls /srv/BKx_programming
> > ls: cannot access /srv/BKx_programming: *No such file or directory*
> > 
>
> In my example I had only setup the automount of BKx_data-personal.
>
> Have you completed it to automount the 3 partitions?
>
> What gives:
>
>   ls /srv/BKx_data-personal
>
> > (the output about the service is :)
> > ---
> > [angelo_dev@localhost ~]$ sudo systemctl status autofs
> > [sudo] password for angelo_dev:
> > * autofs.service - Automounts filesystems on demand
> >Loaded: loaded (/usr/lib/systemd/system/autofs.service; enabled)
> >Active: active (running) since Sun 2018-01-07 17:36:34 IST; 16min ago
>
> What gives (as an attachement):
>
>   journalctl --since 17:36:00 -u autofs.service
>
> > Perhaps the right procedure (in the case of an USB device) is really to
> use
> > the node file in /dev directory how is wrote in the article ?
>
> I don't think so: we do the same with /dev/disk/by-uuid/xxx
>
> --
> francis
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
>
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Data backup- (udev problem)

[Francis . Montagnac]

On Sun, 07 Jan 2018 17:58:07 +0200 Angelo Moreschini wrote:

> I can see the partitions by nautilus as is the standard, but still I cannot
> see them from the command line ..:
> 
> [angelo_dev@localhost ~]$ ls /srv/BKx_programming
> ls: cannot access /srv/BKx_programming: *No such file or directory*
> 

In my example I had only setup the automount of BKx_data-personal.

Have you completed it to automount the 3 partitions?

What gives:

  ls /srv/BKx_data-personal
 
> (the output about the service is :)
> ---
> [angelo_dev@localhost ~]$ sudo systemctl status autofs
> [sudo] password for angelo_dev:
> * autofs.service - Automounts filesystems on demand
>Loaded: loaded (/usr/lib/systemd/system/autofs.service; enabled)
>Active: active (running) since Sun 2018-01-07 17:36:34 IST; 16min ago

What gives (as an attachement):

  journalctl --since 17:36:00 -u autofs.service

> Perhaps the right procedure (in the case of an USB device) is really to use
> the node file in /dev directory how is wrote in the article ?

I don't think so: we do the same with /dev/disk/by-uuid/xxx

-- 
francis
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Data backup- (udev problem)

[Angelo Moreschini]

Hi Francis,

I followed your procedure,

I can see the partitions by nautilus as is the standard, but still I cannot
see them from the command line ..:

[angelo_dev@localhost ~]$ ls /srv/BKx_programming
ls: cannot access /srv/BKx_programming: *No such file or directory*

(the output about the service is :)
---
[angelo_dev@localhost ~]$ sudo systemctl status autofs
[sudo] password for angelo_dev:
● autofs.service - Automounts filesystems on demand
   Loaded: loaded (/usr/lib/systemd/system/autofs.service; enabled)
   Active: active (running) since Sun 2018-01-07 17:36:34 IST; 16min ago
  Process: 1202 ExecStart=/usr/sbin/automount $OPTIONS --pid-file
/run/autofs.pid (code=exited, status=0/SUCCESS)
 Main PID: 1220 (automount)
   CGroup: /system.slice/autofs.service
   └─1220 /usr/sbin/automount --pid-file /run/autofs.pid
=

what to say ??

Perhaps the right procedure (in the case of an USB device) is really to use
the node file in /dev directory how is wrote in the article ?

We tried ... In every case thank you very much

Angelo


On Sun, Jan 7, 2018 at 1:44 PM,  wrote:

>
> On Sun, 07 Jan 2018 13:07:11 +0200 Angelo Moreschini wrote:
>
> > Strangely I had several difficult to try autofs ..
>
> This is not as simple as /etc/fstab.
>
> > Now I that I went more in depth,I can understand that autofs is made
> mainly
> > to be used in a net environment  (NFS - file systems used in networks).
>
> Yes, but not only.
>
> > The purpose because I wont use autofs is different.. :
>
> Again, I'm almost sure you do not need it.
>
> > I wont only to mount an USB Hard Disk - permanently connected to
> > computer .
>
> > The case  that I am interested is not so much considered in current
> > "literature"  and so the
> information
> > that I collected couldn't be, perhaps, appropriate.. ...
>
> > I found only an article that consider explicitly the my  case...:
>
> > *Automatically mount USB external drive with autofs
> > -https://linuxconfig.org/automatically-mount-usb-
> external-drive-with-autofs
>
> > This article suggest to use the file "node" in the directory /dev as name
> > for mounting the partitions...
> > This is another/different way to cope the problem...
>
> > If you are interested, give a look to this article, ...
>
> I read it already.
>
> > perhaps what I did til now (mounting directories instead i file node
> > in /dev directory) could be not the right procedure...
>
> You mounted (in /etc/fstab) using UUIDs, and that is a good practise.
>
> If you really want to test autofs try the following:
>
> Add in /etc/auto.master:
>
>  cut here --
> /srv/   /etc/auto.ext-usb --timeout=10,defaults
>  cut here --
>
> And create /etc/auto.ext-usb as:
>
>  cut here --
> BKx_data-personal   -fstype=ntfs   :/dev/disk/by-uuid/376214F24CC07CE0
>  cut here --
>
> Then restart autofs.service and check that you see your partition
> under /srv/BKx_data-personal/
>
> I reference the partition by its UUID, knowning that the system
> creates automatically the /dev/disk/by-uuid/xxx entries.
>
> autofs wants a :/dev/... as location.
>
> I don't think the options ,user,exec,uid=1000 are needed.
>
> --
> francis
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
>
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Data backup- (udev problem)

[Francis . Montagnac]

On Sun, 07 Jan 2018 13:07:11 +0200 Angelo Moreschini wrote:

> Strangely I had several difficult to try autofs ..

This is not as simple as /etc/fstab.

> Now I that I went more in depth,I can understand that autofs is made mainly
> to be used in a net environment  (NFS - file systems used in networks).

Yes, but not only.

> The purpose because I wont use autofs is different.. :

Again, I'm almost sure you do not need it.

> I wont only to mount an USB Hard Disk - permanently connected to
> computer .

> The case  that I am interested is not so much considered in current
> "literature"  and so the information
> that I collected couldn't be, perhaps, appropriate.. ...

> I found only an article that consider explicitly the my  case...:

> *Automatically mount USB external drive with autofs
> -https://linuxconfig.org/automatically-mount-usb-external-drive-with-autofs

> This article suggest to use the file "node" in the directory /dev as name
> for mounting the partitions...
> This is another/different way to cope the problem...

> If you are interested, give a look to this article, ...

I read it already.

> perhaps what I did til now (mounting directories instead i file node
> in /dev directory) could be not the right procedure...

You mounted (in /etc/fstab) using UUIDs, and that is a good practise.

If you really want to test autofs try the following:

Add in /etc/auto.master:

 cut here --
/srv/   /etc/auto.ext-usb --timeout=10,defaults
 cut here --

And create /etc/auto.ext-usb as:

 cut here --
BKx_data-personal   -fstype=ntfs   :/dev/disk/by-uuid/376214F24CC07CE0
 cut here --

Then restart autofs.service and check that you see your partition
under /srv/BKx_data-personal/

I reference the partition by its UUID, knowning that the system
creates automatically the /dev/disk/by-uuid/xxx entries.

autofs wants a :/dev/... as location.
 
I don't think the options ,user,exec,uid=1000 are needed.

-- 
francis
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Data backup- (udev problem)

[Angelo Moreschini]

Hi Francis,

before to begin, I would like talk with you a moment...

Strangely I had several difficult to try autofs ..

Now I that I went more in depth,I can understand that autofs is made mainly
to be used in a net environment  (NFS - file systems used in networks).

The purpose because I wont use autofs is different.. : I wont only to mount
an USB Hard Disk - permanently connected to computer .

The case  that I am interested is not so much considered in current
"literature"  and so the information
that I collected couldn't be, perhaps, appropriate.. ...
I found only an article that consider explicitly the my  case...:
*Automatically mount USB external drive with autofs
-https://linuxconfig.org/automatically-mount-usb-external-drive-with-autofs
*

This article suggest to use the file "node" in the directory /dev as name
for mounting the partitions...
This is another/different way to cope the problem...

If you are interested, give a look to this article, ... perhaps what I did
til now (mounting directories instead i file node in /dev directory) could
be not the right procedure...

 Thank you

Angelo




On Sun, Jan 7, 2018 at 12:16 PM, Angelo Moreschini <
mrangelo.fed...@gmail.com> wrote:

>  I understood (now) from where the error came :
>
> in auto.master file I forgot to put in comment this line :
> <+auto.master>
>
> Do you know what means it ? (what is the purpose of the sign "+"  ?).
>
> Now I''l try your suggestion :  directory>..
>
>
> On Sun, Jan 7, 2018 at 11:58 AM,  wrote:
>
>>
>> On Sun, 07 Jan 2018 11:43:37 +0200 Angelo Moreschini wrote:
>>
>> > I understand what you say Francis, perhaps you are right, and I'll try
>> your
>> > suggestion.
>>
>> Ok.
>>
>> > But first of all I would like fix the basic problem (that the service
>> > doesn't correctly).
>>
>> You mean I think the autofs service.
>>
>> If I understand correctly your setup, your USB disk is always attached
>> to your machine, thus using autofs is useless.
>>
>> > All the tray that I can do before to solve this, could be affected from
>> > this  "original sin"...
>>
>> I don't think so: this affect only autofs.
>>
>> > It is not so much material finding for :
>> > *"automount[1214]: setautomntent: lookup(sss): setautomntent: No such
>> file
>> > or directory"*
>>
>> > and I, also, am not able to understand exactly the meaning of this
>> message.
>>
>> I suspect that you have in the /etc/nsswitch.conf file:
>>
>>   automount:  files sss
>>
>> and then autofs (the automount process) if attempting to find its
>> auto.master map in /etc (files) then with an sss lookup.
>>
>> --
>> francis
>> ___
>> users mailing list -- users@lists.fedoraproject.org
>> To unsubscribe send an email to users-le...@lists.fedoraproject.org
>>
>
>
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Data backup- (udev problem)

[Francis . Montagnac]

On Sun, 07 Jan 2018 12:16:34 +0200 Angelo Moreschini wrote:

>  I understood (now) from where the error came :

> in auto.master file I forgot to put in comment this line :
> <+auto.master>

> Do you know what means it ? (what is the purpose of the sign "+"  ?).

Search using nsswitch.conf a map of name auto.master. Details in the
man of auto.master.

-- 
francis
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Data backup- (udev problem)

[Angelo Moreschini]

 I understood (now) from where the error came :

in auto.master file I forgot to put in comment this line :
<+auto.master>

Do you know what means it ? (what is the purpose of the sign "+"  ?).

Now I''l try your suggestion : ..


On Sun, Jan 7, 2018 at 11:58 AM,  wrote:

>
> On Sun, 07 Jan 2018 11:43:37 +0200 Angelo Moreschini wrote:
>
> > I understand what you say Francis, perhaps you are right, and I'll try
> your
> > suggestion.
>
> Ok.
>
> > But first of all I would like fix the basic problem (that the service
> > doesn't correctly).
>
> You mean I think the autofs service.
>
> If I understand correctly your setup, your USB disk is always attached
> to your machine, thus using autofs is useless.
>
> > All the tray that I can do before to solve this, could be affected from
> > this  "original sin"...
>
> I don't think so: this affect only autofs.
>
> > It is not so much material finding for :
> > *"automount[1214]: setautomntent: lookup(sss): setautomntent: No such
> file
> > or directory"*
>
> > and I, also, am not able to understand exactly the meaning of this
> message.
>
> I suspect that you have in the /etc/nsswitch.conf file:
>
>   automount:  files sss
>
> and then autofs (the automount process) if attempting to find its
> auto.master map in /etc (files) then with an sss lookup.
>
> --
> francis
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
>
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Data backup- (udev problem)

[Francis . Montagnac]

On Sun, 07 Jan 2018 11:43:37 +0200 Angelo Moreschini wrote:

> I understand what you say Francis, perhaps you are right, and I'll try your
> suggestion.

Ok.

> But first of all I would like fix the basic problem (that the service
> doesn't correctly).

You mean I think the autofs service.

If I understand correctly your setup, your USB disk is always attached
to your machine, thus using autofs is useless.

> All the tray that I can do before to solve this, could be affected from
> this  "original sin"...

I don't think so: this affect only autofs.

> It is not so much material finding for :
> *"automount[1214]: setautomntent: lookup(sss): setautomntent: No such file
> or directory"*

> and I, also, am not able to understand exactly the meaning of this message.

I suspect that you have in the /etc/nsswitch.conf file:

  automount:  files sss

and then autofs (the automount process) if attempting to find its
auto.master map in /etc (files) then with an sss lookup.

-- 
francis
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Data backup- (udev problem)

[Angelo Moreschini]

I understand what you say Francis, perhaps you are right, and I'll try your
suggestion.

But first of all I would like fix the basic problem (that the service
doesn't correctly).
All the tray that I can do before to solve this, could be affected from
this  "original sin"...

It is not so much material finding for :
*"automount[1214]: setautomntent: lookup(sss): setautomntent: No such file
or directory"*

and I, also, am not able to understand exactly the meaning of this message.





On Sun, Jan 7, 2018 at 10:44 AM,  wrote:

>
> Hi.
>
> On Wed, 27 Dec 2017 11:24:06 +0200 Angelo Moreschini wrote:
> ...
> > 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
>
> You are using the UUIDs which is fine: no need thus to configure udev
> to have a fixed device name for those partitions.
>
> > 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 suspect that nautilus is in some manner auditing what resides under
> /media, and unmounting the partitions when not in use.
>
> Can you try to do your mounts under some other directory (ex: /srv)?
>
> --
> francis
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
>
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Data backup- (udev problem)

[Francis . Montagnac]

Hi.

On Wed, 27 Dec 2017 11:24:06 +0200 Angelo Moreschini wrote:
...
> 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

You are using the UUIDs which is fine: no need thus to configure udev
to have a fixed device name for those partitions.

> 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 suspect that nautilus is in some manner auditing what resides under
/media, and unmounting the partitions when not in use.

Can you try to do your mounts under some other directory (ex: /srv)?

-- 
francis
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Data backup- (udev problem)

[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
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Data backup- (udev problem)

[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.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Data backup- (udev problem)

[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?
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Data backup- (udev problem)

[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 ).*
> 
> 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.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Data backup- (udev problem)

[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 ).*

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 -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
>
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Data backup- (udev problem)

[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.

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Data backup- (udev problem)

[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.

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Data backup- (udev problem)

[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 <
mrangelo.fed...@gmail.com> 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  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
> 

Re: Data backup- (udev problem)

[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  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 -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
>
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Data backup- (udev problem)

[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.

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Data backup- (udev problem)

[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

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Data backup- (udev problem)

[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 -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
>
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Data backup- (udev problem)

[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
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org