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[,...]] <device|image_file 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/1 S+ 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, <francis.montag...@inria.fr> 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 -- 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
