Erm ... the noauto should be part of the options column, so append it to the previous option (and of course delimit with a ",").
I see that the '.automount' was not generated ... Maybe it's related to the noauto issue.
By the way , "mount -a" should complain if fstab is not OK.
Best Regards,
Strahil Nikolov
В неделя, 3 януари 2021 г., 21:01:29 Гринуич+2, Fred <fred.fredex@xxxxxxxxx> написа:
$ cat /etc/centos-release
CentOS Linux release 7.9.2009 (Core)
$ sudo systemctl status mnt-backup.mount mnt-backup.automount
[sudo] password for fredex:
● mnt-backup.mount - /mnt/backup
Loaded: loaded (/etc/fstab; bad; vendor preset: disabled)
Active: active (mounted) since Sat 2021-01-02 22:20:05 EST; 14h ago
Where: /mnt/backup
What: /dev/sdc1
Docs: man:fstab(5)
man:systemd-fstab-generator(8)
Tasks: 0
● mnt-backup.automount
Loaded: loaded
Active: inactive (dead)
Where: /mnt/backup
[fredex@fcshome Desktop]$ systemctl cat mnt-backup.mount mnt-backup.automount
No files found for mnt-backup.automount.
# /run/systemd/generator/mnt-backup.mount
# Automatically generated by systemd-fstab-generator
[Unit]
SourcePath=/etc/fstab
Documentation=man:fstab(5) man:systemd-fstab-generator(8)
RequiresOverridable=systemd-fsck@dev-disk-by\x2duuid-259ec5ea\x2de8a4\x2d465a\x2
After=systemd-fsck@dev-disk-by\x2duuid-259ec5ea\x2de8a4\x2d465a\x2d9263\x2d1c062
[Mount]
What=/dev/disk/by-uuid/259ec5ea-e8a4-465a-9263-1c06217b9aaf
Where=/mnt/backup
Type=ext4
Options=noauto
the fstab statement I put in my last posting was a copy/paste from /etc/fstab, so it should be correct as shown. I don't see a comma before noauto.
On Sun, Jan 3, 2021 at 11:42 AM Strahil Nikolov <hunter86_bg@xxxxxxxxx> wrote:
> Are you still on 7.6 ? I recently discovered that a bug in sysstat was fixed in 7.7 that prevented autofs from umounting the filesystem.
>
> The following should show if it's taking into action:
> systemctl status mnt-backup.mount mnt-backup.automount
> systemctl cat mnt-backup.mount mnt-backup.automount
>
>
> Are you sure that you got no "," before that "noauto" ?
>
> Best Regards,
> Strahil Nikolov
>
>
>
>
>
>
> В неделя, 3 януари 2021 г., 16:25:47 Гринуич+2, Fred <fred.fredex@xxxxxxxxx> написа:
>
>
>
>
>
> Strahil:
>
> I WAS using that, but the automatic umount never worked, leaving it mounted all the time.
>
> 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
>
> which is exactly as it was before except for the x-systemd entries as you described.
>
> and the peculiar thing is it STILL does not automount. and yes, I did do systemctl restart local-fs.target.
>
> do I need to reboot (or something simpler, maybe) to fully disable the auto.master stuff?
>
> Thanks again!
>
> Fred
>
> On Sun, Jan 3, 2021 at 5:54 AM Strahil Nikolov via CentOS <centos@xxxxxxxxxx> wrote:
>> Hi Fred,
>>
>> do you use automatic umount for the map in /etc/auto.master (--timeout) ?
>>
>> If yes, then the systemd mount options probably won't help.
>>
>> Best Regards,
>> Strahil Nikolov
>>
>>
>>
>>
>>
>>
>>
>>
>> В неделя, 3 януари 2021 г., 04:27:17 Гринуич+2, Fred <fred.fredex@xxxxxxxxx> написа:
>>
>>
>>
>>
>>
>> Yeah, and the instructions for setting RAID-1 or RAID-0 have the switch
>> positions exactly reversed.
>>
>> Strahil: I'm using autofs to automount the unit. but just turned that off
>> and enabled the xsystemd.automount in fstab, we'll see how that works.
>>
>> Fred
>>
>>
>> On Sat, Jan 2, 2021 at 4:11 PM Warren Young <warren@xxxxxxxxxxx> wrote:
>>
>>> On Jan 2, 2021, at 11:17 AM, Fred <fred.fredex@xxxxxxxxx> wrote:
>>> >
>>> > I assume that the yottamaster device runs Linux, just like 99% of other
>>> > such devices.
>>>
>>> 99% of NAS boxes, maybe, but not dumb RAID boxes like the one I believe
>>> you’re referring to.
>>>
>>> (And I doubt even that, with the likes of FreeNAS extending down from the
>>> enterprise space where consumer volume can affect that sort of thing.)
>>>
>>> I have more than speculation to back that guess: the available firmware
>>> images are far too small to contain a Linux OS image, their manuals don’t
>>> talk about Linux or GPL that I can see, and there’s no place to download
>>> their Linux source code per the GPL.
>>>
>>> While doing this exploration, I’ve run into multiple problems with their
>>> web site, which strengthens my suspicion that this box is your culprit. If
>>> they’re this slipshod with their marketing material, what does that say
>>> about their engineering department?
>>> _______________________________________________
>>> CentOS mailing list
>>> CentOS@xxxxxxxxxx
>>> https://lists.centos.org/mailman/listinfo/centos
>>
>>>
>> _______________________________________________
>> CentOS mailing list
>> CentOS@xxxxxxxxxx
>> https://lists.centos.org/mailman/listinfo/centos
>> _______________________________________________
>> CentOS mailing list
>> CentOS@xxxxxxxxxx
>> https://lists.centos.org/mailman/listinfo/centos
>>
>
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
https://lists.centos.org/mailman/listinfo/centos
