Date: Wed, 7 Apr 2010 23:21:53 +0930 From: Rob <listone@deathbeforedecaf.net> To: Tim Daneliuk <tundra@tundraware.com> Cc: FreeBSD Mailing List <freebsd-questions@freebsd.org> Subject: Re: Preventing Bad SMB Mount From Stalling A Boot Message-ID: <830D19B5-4BA6-42B9-B2D1-1833EC04252C@deathbeforedecaf.net> In-Reply-To: <4BBB56E2.10801@tundraware.com> References: <4BBB56E2.10801@tundraware.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 = like=20 > this: >=20 > //USER@WINSERVER/SHARE /mountpoint smbfs rw 0 0 >=20 > 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. >=20 > 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 = of on=20 boot. It doesn't directly support SMB, but it may be possible to to = combine=20 them: http://www.jiegao.co.cc/computer-notes/unix-tips/freebsd-amd-for-samba Rob.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?830D19B5-4BA6-42B9-B2D1-1833EC04252C>