From owner-freebsd-hackers@FreeBSD.ORG Fri Mar 2 16:44:18 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0059616A401 for ; Fri, 2 Mar 2007 16:44:17 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: from multiplay.co.uk (core6.multiplay.co.uk [85.236.96.23]) by mx1.freebsd.org (Postfix) with ESMTP id 9449013C481 for ; Fri, 2 Mar 2007 16:44:17 +0000 (UTC) (envelope-from killing@multiplay.co.uk) X-Spam-Checker-Version: SpamAssassin 3.1.5 (2006-08-29) on core6.multiplay.co.uk X-Spam-Level: X-Spam-Status: No, score=-24.7 required=6.0 tests=BAYES_00, USER_IN_WHITELIST, USER_IN_WHITELIST_TO autolearn=ham version=3.1.5 Received: from vader ([212.135.219.179]) by multiplay.co.uk (multiplay.co.uk [85.236.96.23]) (MDaemon PRO v9.5.4) with ESMTP id md50003578980.msg for ; Fri, 02 Mar 2007 16:43:02 +0000 Message-ID: <015601c75ce9$d0263a10$b3db87d4@multiplay.co.uk> From: "Steven Hartland" To: Date: Fri, 2 Mar 2007 16:42:41 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3028 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 X-MDRemoteIP: 212.135.219.179 X-Return-Path: killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk X-MDaemon-Deliver-To: freebsd-hackers@freebsd.org X-Spam-Processed: multiplay.co.uk, Fri, 02 Mar 2007 16:43:03 +0000 X-MDAV-Processed: multiplay.co.uk, Fri, 02 Mar 2007 16:43:04 +0000 Subject: NFS based /usr prevents normal startup due to slow net init X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Mar 2007 16:44:18 -0000 Another observation from my recent dealings with using NFS based /usr is that the remote critical mounts via nfs dont always give the network enough time to initialise before running. The first error displayed is: Mounting NFS file systems:mount_nfs: nfs1: hostname nor servname provided, or not known This is particularly noticeable when the machine is connected to Cisco equipment as they take quite a while link to the connected host after initialisation. The result of this is that other services such as ldconfig fail to initialise properly due to the mount not being available until some point later in the boot process once link has been established. Has anyone else experienced this? Should mountcritremote use "mount -a -t nfs" when this appears to return after a short period without said FS's being successfully mounted? Is there a way to ensure that mount doesnt return without success i.e. a missing flag in my fstab or should mountcritremote be updated to test for failure and retry? This was bought up some time ago on the current list but no answers where forth coming: http://lists.freebsd.org/pipermail/freebsd-current/2005-December/058935.html Test details: Network card: bge0 Switch: Cisco 6509 Switch Blade: WS-X6748-GE-TX fstab line: nfs1:/fs/usr /usr nfs rw 0 0 Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk.