Date: Mon, 5 Jan 1998 22:29:39 +0100 From: Andreas Klemm <andreas@klemm.gtn.com> To: =?iso-8859-1?Q?=22Luis_E=2E_Mu=F1oz=22?= <lem@cantv.net> Cc: spork <spork@super-g.com>, jbutt@mwci.net, freebsd-isp@FreeBSD.ORG Subject: 2.2-STABLE client hangs after a NFS server (2.2-STABLE) reboot (was: Re: [fbsd-isp] Designing for a very large ISP) Message-ID: <19980105222939.65169@klemm.gtn.com> In-Reply-To: =?iso-8859-1?Q?=3C3=2E0=2E5=2E32=2E19980104225625=2E007bb280=40pop=2Ecan?= =?iso-8859-1?Q?tv=2Enet=3E=3B_from_=22Luis_E=2E_Mu=F1oz=22_on_Sun=2C_Jan?= =?iso-8859-1?Q?_04=2C_1998_at_10=3A56=3A25PM_-0400?= References: <199801042025.OAA22797@subcellar.mwci.net> <Pine.BSF.3.96.980104164317.17626C-100000@super-g.inch.com> <3.0.5.32.19980104225625.007bb280@pop.cantv.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Jan 04, 1998 at 10:56:25PM -0400, "Luis E. Muņoz" wrote: > At 04:50 PM 04/01/1998 -0500, spork wrote: > > A panic is definitely not correct, however a command waiting forever > is normal. These are the semantics of a 'hard' mount on NFS. If you > want the processes to timeout, you need a 'soft' mount. When using hard mounts the client should only wait for the server to come up again. I also noticed with FreeBSD-stable, that the client still hangs, if the server was down and reboots afterwards ... this was using the amd automounter. The soft mount only makes it possible for the NFS client not to wait for the server, which is really not recommended because of the possibility of data lossage. When using Solaris 1 or 2 I'm used, that the clients can continue to work, if the NFS server comes uo again. FreeBSD fails here. Is this a known problem ? -- Andreas Klemm powered by ,,symmetric multiprocessor FreeBSD''
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980105222939.65169>