# Autofs failing to remount shares after they expire

**URL:** <https://forums.rockylinux.org/t/autofs-failing-to-remount-shares-after-they-expire/14336>\
**Category:** Rocky Linux Help & Support\
**Tags:** rocky-linux-8\
**Created:** [May 30, 2024, 8:58pm UTC](https://forums.rockylinux.org/t/autofs-failing-to-remount-shares-after-they-expire/14336 "2024-05-30T20:58:03Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![nm\_ai](https://avatars.discourse-cdn.com/v4/letter/n/59ef9b/32.png) [@nm\_ai](https://forums.rockylinux.org/u/nm_ai)\
**Post date:** [May 30, 2024, 8:58pm UTC](https://forums.rockylinux.org/t/autofs-failing-to-remount-shares-after-they-expire/14336/1 "2024-05-30T20:58:03Z")

</div>

While upgrading some hosts from Centos 7 to Rocky 8, autofs appears to be unable to remount mounts after they expire (using the same autofs config files).

Mount config:  
auto.master:  
/mounts/programs/prog\_m /etc/auto.programs\_prog\_m tcp hard intr timeo=600 retrans=2 async --ghost

auto.programs\_prog\_m:  
production -fstype=nfs4 /incoming fileserver:/ifs/incoming/aibs/prog\_m  
/omf fileserver:/ifs/programs/prog\_m/production/omf  
/oscope fileserver:/ifs/programs/prog\_m/production/oscope  
/learn fileserver:/ifs/programs/prog\_m/production/learn  
/dynamic fileserver:/ifs/programs/prog\_m/production/dynamic  
/info fileserver:/ifs/programs/prog\_m/production/info  
/var fileserver:/ifs/programs/prog\_m/production/var  
/task fileserver:/ifs/programs/prog\_m/production/task  
/psy fileserver:/ifs/programs/prog\_m/production/psy  
/u01 fileserver:/ifs/programs/prog\_m/production/u01  
/vip fileserver:/ifs/programs/prog\_m/production/vip

While things work:  
pwd; ls  
/mount/programs/prog\_m/production  
dynamic incoming info learn omf oscope task psy u01 var vip

Break:  
Same path, different contents:  
pwd; ls  
/mounts/programs/prog\_m/production  
info omf

Turning on logging at debug on autofs and I can see the mounts expiring:  
May 30 11:06:12 automount[46872]: expire\_proc\_indirect: expire /mounts/programs/prog\_m/production  
…  
May 30 11:06:15 automount[46872]: st\_expire: state 1 path /mounts/programs/prog\_m  
…  
May 30 11:06:16 automount[46872]: expire\_proc\_indirect: expire /mounts/programs/prog\_m/production  
May 30 11:06:16 automount[46872]: expire\_proc\_indirect: 2 remaining in /mounts/programs/prog\_m  
May 30 11:06:16 automount[46872]: expire\_cleanup: got thid 140227066693376 path /mounts/programs/prog\_m stat 2  
May 30 11:06:16 automount[46872]: expire\_cleanup: sigchld: exp 140227066693376 finished, switching from 2 to 1  
May 30 11:06:16 automount[46872]: st\_ready: st\_ready(): state = 2 path /mounts/programs/prog\_m  
…  
May 30 11:06:21 automount[46872]: expiring path /mounts/programs/prog\_m/production  
May 30 11:06:21 automount[46872]: umount\_multi: path /mounts/programs/prog\_m/production incl 1  
May 30 11:06:21 automount[46872]: tree\_mapent\_umount\_offset: umount offset /mounts/programs/prog\_m/production/dynamic  
May 30 11:06:21 automount[46872]: umounted offset mount /mounts/programs/prog\_m/production/dynamic  
May 30 11:06:21 automount[46872]: tree\_mapent\_umount\_offset: umount offset /mounts/programs/prog\_m/production/incoming  
May 30 11:06:21 automount[46872]: umounted offset mount /mounts/programs/prog\_m/production/incoming  
May 30 11:06:21 automount[46872]: tree\_mapent\_umount\_offset: umount offset /mounts/programs/prog\_m/production/info  
…  
May 30 11:06:22 automount[46872]: tree\_mapent\_delete\_offset\_tree: deleting offset key /mounts/programs/prog\_m/production/dynamic  
May 30 11:06:22 automount[46872]: tree\_mapent\_delete\_offset\_tree: deleting offset key /mounts/programs/prog\_m/production/info  
May 30 11:06:22 automount[46872]: tree\_mapent\_delete\_offset\_tree: deleting offset key /mounts/programs/prog\_m/production/incoming  
May 30 11:06:22 automount[46872]: tree\_mapent\_delete\_offset\_tree: deleting offset key /mounts/programs/prog\_m/production/learn  
May 30 11:06:22 automount[46872]: tree\_mapent\_delete\_offset\_tree: deleting offset key /mounts/programs/prog\_m/production/oscope  
May 30 11:06:22 automount[46872]: tree\_mapent\_delete\_offset\_tree: deleting offset key /mounts/programs/prog\_m/production/psy  
May 30 11:06:22 automount[46872]: tree\_mapent\_delete\_offset\_tree: deleting offset key /mounts/programs/prog\_m/production/task  
May 30 11:06:22 automount[46872]: tree\_mapent\_delete\_offset\_tree: deleting offset key /mounts/programs/prog\_m/production/omf  
May 30 11:06:22 automount[46872]: tree\_mapent\_delete\_offset\_tree: deleting offset key /mounts/programs/prog\_m/production/var  
May 30 11:06:22 automount[46872]: tree\_mapent\_delete\_offset\_tree: deleting offset key /mounts/programs/prog\_m/production/vip  
May 30 11:06:22 automount[46872]: tree\_mapent\_delete\_offset\_tree: deleting offset key /mounts/programs/prog\_m/production/u01  
May 30 11:06:22 automount[46872]: expired /mounts/programs/prog\_m/production  
…  
May 30 11:06:22 automount[46872]: expire\_proc\_indirect: expire /mounts/programs/prog\_m/production  
May 30 11:06:22 automount[46872]: expire\_proc\_indirect: 1 remaining in /mounts/programs/prog\_m  
May 30 11:06:22 automount[46872]: expire\_cleanup: got thid 140227066693376 path /mounts/programs/prog\_m stat 2  
May 30 11:06:22 automount[46872]: expire\_cleanup: sigchld: exp 140227066693376 finished, switching from 2 to 1  
May 30 11:06:22 automount[46872]: st\_ready: st\_ready(): state = 2 path /mounts/programs/prog\_m

Later I see a “handle\_packet\_missing\_indirect: token 13149, name prog\_m” error as well

On trying to access the shares within /mounts/programs/prog\_m/production, I get a wedged `ls` on the 1-2 shares that remain (in the break note above: “info omf” both break). I can `ls` on the directories that should be in there, and I get a “No such file or directory”

Restarting autofs brings everything back again, but fails soon after. This almost feels like a nested mount issue, but why has this worked historically? Anyone else see this / able to point me in a direction?

Many thanks!

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex020/uploads/rockylinux/original/1X/91b7219eec10e30013422e4df76c1d898711a5d5.svg) [@system](https://forums.rockylinux.org/u/system)\
**Post date:** [July 29, 2024, 8:58pm UTC](https://forums.rockylinux.org/t/autofs-failing-to-remount-shares-after-they-expire/14336/2 "2024-07-29T20:58:52Z")

</div>

Closed on July 29, 2024, 8:58pm UTC

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
