amd automounting daemon is unreliable

Nathan Butcher n-butcher at
Tue Aug 25 05:33:38 UTC 2009

I'm having some troublesome issues with filesystems mounted with amd in

We have a backend file server wwith sharenfs attributes from ZFS
displaying NFS mountpoints to our front end machines:-

tank/export  mountpoint     /export                       local
tank/export  sharenfs       -maproot=0:0 server1 server2  local

and we have amd automounting directories on the backend file system


/defaults       type:=nfs;rhost:=wrfs;opts:=rw,vers=3,proto=udp,nodev
*               rfs=/export/files/${key}


amd_flags="-a /.amd_mnt -l syslog /files /etc/amd.d/"

There are a bunch of subdirectories in /files which get mounted across
the network when they are accessed on the front-end, and as a solution -
this has been working well.

...the PROBLEM is that it is unreliable. Sometimes amd hangs, and a
mounted directory - while listed in df becomes inaccessible and I get
"Permission Denied" errors while trying to access the mounted directory.
I'm using some monitoring on the amd process, but as it doesn't die to
trigger an alert, I have to wait until someone tells me that the
filesystem is rejecting them in order to respond tot he issue.

It also happens way too often for me to continue using this solution.
Unless I script amd to restart itself continuously in the event of a
crash... I cannot use it in a production environment.

フュージョン・ネットワークサービス株式会社 ■楽天ブロードバンド■
GOL事業部 システム技術部 ネットワーク・オペレションズ グループ
Nathan Butcher / phone +81-50-5527-3611 / fax +81-3-3262-2224

More information about the freebsd-questions mailing list