Date: Tue, 06 Apr 2010 13:50:19 -0500 From: Tim Daneliuk <tundra@tundraware.com> To: FreeBSD Mailing List <freebsd-questions@freebsd.org> Subject: Re: Preventing Bad SMB Mount From Stalling A Boot Message-ID: <4BBB826B.5020500@tundraware.com> In-Reply-To: <r2rcf9b1ee01004061136j1a80daaei298be9f85ee29980@mail.gmail.com> References: <r2rcf9b1ee01004061136j1a80daaei298be9f85ee29980@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 4/6/2010 1:36 PM, Dan Naumov wrote: >> I mount my SMB shares from /etc/fstab on a FBSD 8.x production machine like >> this: >> >> //USER at WINSERVER/SHARE /mountpoint smbfs rw 0 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? > > A bit of an ugly hack, but have you considered attempting to mount the > share via an automatic script after the system has finished booting? > > - Sincerely, > Dan Naumov Actually that is what I was doing via a script in /usr/local/etc/rc.d before I switched over to the /etc/fstab scheme. I may have to fall back to the rc.d approach. It seems odd to me that there's "best effort to mount" semantic option for fstab entries... -- ---------------------------------------------------------------------------- Tim Daneliuk tundra@tundraware.com PGP Key: http://www.tundraware.com/PGP/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4BBB826B.5020500>