From owner-freebsd-questions@FreeBSD.ORG Tue Apr 27 02:10:27 2010 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 9E19A1065676 for ; Tue, 27 Apr 2010 02:10:27 +0000 (UTC) (envelope-from jamesbrandongooch@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.223.182]) by mx1.freebsd.org (Postfix) with ESMTP id 622BB8FC19 for ; Tue, 27 Apr 2010 02:10:27 +0000 (UTC) Received: by iwn12 with SMTP id 12so2627724iwn.15 for ; Mon, 26 Apr 2010 19:10:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=PB0/bG582Qs+YAlnG8ILQ4bvvXBG/h1b0V2v+kEugq4=; b=QOgCBjmP3DfxuLXBSV/P+K4Vj7Vew5vaUZYU5HVdEQhxQRY6qFspdyfYxPYVXxbDPO TfBVudq6ysQKpeKwNxXXTv2NgTH/D93qHO/bimWXPkqdjx1kvOjY6Cj8u9nSmTIC4E7v Qja089KiHuSSHYXJ0qj4O7T4im0gbqTD48XdU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=ZevI9/aENxH1C1HTf6vnTG6VqFHPSexMTCq9Hb4/2baIwT729CWub0coowlW1qDq7W ZQ9B77EC4BhRcavx8Fkfjg5Jld4f+4X9eqfhohmyquYnP/TX6jhp8tycKpAQAub82bNd mA4UCrw+11ZaezRAY7HfkMXKAYodIbh2DBfpk= MIME-Version: 1.0 Received: by 10.231.143.137 with SMTP id v9mr1637274ibu.70.1272334217415; Mon, 26 Apr 2010 19:10:17 -0700 (PDT) Received: by 10.231.113.36 with HTTP; Mon, 26 Apr 2010 19:10:17 -0700 (PDT) In-Reply-To: <830D19B5-4BA6-42B9-B2D1-1833EC04252C@deathbeforedecaf.net> References: <4BBB56E2.10801@tundraware.com> <830D19B5-4BA6-42B9-B2D1-1833EC04252C@deathbeforedecaf.net> Date: Mon, 26 Apr 2010 21:10:17 -0500 Message-ID: From: Brandon Gooch To: Rob Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Tim Daneliuk , FreeBSD Mailing List Subject: Re: Preventing Bad SMB Mount From Stalling A Boot 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, 27 Apr 2010 02:10:27 -0000 On Wed, Apr 7, 2010 at 8:51 AM, Rob wrote: > On 07/04/2010, at 1:14 AM, Tim Daneliuk wrote: > >> I mount my SMB shares from /etc/fstab on a FBSD 8.x production machine l= ike >> this: >> >> //USER@WINSERVER/SHARE =A0 /mountpoint =A0 =A0smbfs =A0 rw =A0 =A0 =A0 = =A0 =A00 =A0 =A0 =A0 0 >> >> The problem is that after an outage, "WINSERVER" doesn't come up >> before the FBSD machine. So, the FBSD machine tries to boot and then >> hangs permanently because it cannot get the SMB share points mounted. >> This recently happened after a catastrophic power outage that cooked >> the share info on "WINSERVER". Even after it came up, it was no longer >> serving the proper shares and the FBSD machine could never find the >> SMB shares and thus hung permanently. >> >> The SMB mounts are not essential for systems operations. Is there a >> way to tell the FBSD to try and mount SMB, but keep going and complete >> the boot if it cannot? > > In an NFS environment, amd(8) is used to mount shares on demand instead o= f on > boot. It doesn't directly support SMB, but it may be possible to to combi= ne > them: > > =A0http://www.jiegao.co.cc/computer-notes/unix-tips/freebsd-amd-for-samba > > Rob. Wow. Thanks for the link. I really AM a newb when it comes down to it, I didn't even know this was possible with amd(8). Add to the reading list `info am-utils`... Perhaps the information at the link: http://www.jiegao.co.cc/computer-notes/unix-tips/freebsd-amd-for-samba could someday be added to the handbook under "29.3.5 Automatic Mounts with = amd": http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/book.html#NETWORK= -AMD At least in the future these two links will be in the same place for another user's benefit :) -Brandon