OK, I think I've got it set up as described here, while fixing the
misplaced fields in /etc/fstab:
UUID=259ec5ea-e8a4-465a-9263-1c06217b9aaf /mnt/backup ext4
x-systemd.automount,x-systemd.idle-timeout=15min,noauto 0 2
now when I do, e.g., "ls /mnt/backup"
I get:
$ sudo !!
sudo ls /mnt/backup
ls: cannot open directory /mnt/backup: No such file or directory
if I do:
ls /mnt
I see:
backup
use su to become root, then:
ls -l /mnt shows:
# ls -al
total 4
drwxr-xr-x. 3 root root 0 Jan 2 13:24 .
dr-xr-xr-x. 21 root root 4096 Jan 2 09:22 ..
dr-xr-xr-x. 2 root root 0 Jan 2 13:24 backup
ls backup shows:
# ls -al backup
ls: cannot open directory backup: No such file or directory
why? it clearly appears to exist ????
the FS isn't mounted, but /mnt/backup exists, so it should be visible as an
entry directory. also, I can mount it manually:
mount UUID=259ec5ea-e8a4-465a-9263-1c06217b9aaf /mnt/backup
and then access it. but it doesn't automount with, e.g. "ls
/mnt/backup" or
"ls /mnt/backup/backups".
I must still be doing something wrong but maybe I'm too stupid to see it.
(Please don't agree with me publicly...! :=) )
Fred
On Sun, Jan 3, 2021 at 4:36 PM Pete Biggs <pete at biggs.org.uk> wrote:
> >
> > I commented out those entries in /etc/auto.master before modifying the
> > fstab entry:
> >
> > UUID=259ec5ea-e8a4-465a-9263-1c06217b9aaf /mnt/backup
> > ext4,x-systemd.automount,x-systemd.idle-timeout=15min noauto 0
2
>
> That's not correct. See 'man fstab'. It should be
>
> device mount-point filesystem-type options dump fsck
>
> So you should have:
>
> UUID=259ec5ea-e8a4-465a-9263-1c06217b9aaf /mnt/backup ext4
> x-systemd.automount,x-systemd.idle-timeout=15min,noauto 0 2
>
>
> >
> > which is exactly as it was before except for the x-systemd entries as
you
> > described.
>
> Yeah, you put them in the wrong place.
>
>
> P.
>
>
> _______________________________________________
> CentOS mailing list
> CentOS at centos.org
> https://lists.centos.org/mailman/listinfo/centos
>