From owner-freebsd-questions@FreeBSD.ORG Tue Aug 25 05:33:38 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D5928106568D for ; Tue, 25 Aug 2009 05:33:38 +0000 (UTC) (envelope-from n-butcher=freebsd-questions=freebsd.org=xnhrueqv@fusiongol.com) Received: from smtp11.dentaku.gol.com (smtp11.dentaku.gol.com [203.216.5.73]) by mx1.freebsd.org (Postfix) with ESMTP id A953A8FC17 for ; Tue, 25 Aug 2009 05:33:38 +0000 (UTC) Received: from pat.gol.ad.jp ([203.216.1.191] helo=[172.16.1.151]) by smtp11.dentaku.gol.com with esmtpsa (Dentaku) id 1MfoLr-0005a6-7y for ; Tue, 25 Aug 2009 14:13:47 +0900 Message-ID: <4A93730A.8020807@fusiongol.com> Date: Tue, 25 Aug 2009 14:13:46 +0900 From: Nathan Butcher User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: freebsd-questions@freebsd.org X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV GOL (outbound) X-Abuse-Complaints: abuse@gol.com Subject: amd automounting daemon is unreliable X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Aug 2009 05:33:38 -0000 I'm having some troublesome issues with filesystems mounted with amd in FreeBSD 7.2-RELEASE 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 /etc/amd.d/amd.map.export:- /defaults type:=nfs;rhost:=wrfs;opts:=rw,vers=3,proto=udp,nodev * rfs=/export/files/${key} /etc/rc.conf:- amd_enable="YES" amd_flags="-a /.amd_mnt -l syslog /files /etc/amd.d/amd.map.export" 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 https://secure3.gol.com/mod-pl/ols/index.cgi/?intr_id=F-2xsg6jS4u655