Date: Fri, 8 Jul 2005 14:54:44 -0700 (PDT) From: Mohan Srinivasan <mohan_srinivasan@yahoo.com> To: Oliver Lehmann <lehmann@ans-netz.de>, freebsd-current@freebsd.org Subject: Re: problems with soft-nfs when the server goes down Message-ID: <20050708215444.50691.qmail@web80602.mail.yahoo.com> In-Reply-To: <20050708222246.630c9de3.lehmann@ans-netz.de>
next in thread | previous in thread | raw e-mail | index | archive | help
FYI - I am not able to reproduce the problem in my setup (at least not easily). So a tcpdump and core would be very helpful. mohan --- Oliver Lehmann <lehmann@ans-netz.de> wrote: > Hi, > > I belive, everyone who is dealing with NFS knows the following situation: > > Work with a nfs mounted filesystem, while the NFS-server got unavailable > results in locked processes. That is OK because the processes are > unlocked again and will continue with their work when the server is back > online. > So far so good. That was the situation on all FreeBSD I used before. (3.3 > - 5.4) > > Now my NFS-nt is running 6-CURRENT and my NFS-server still runs 5.4 > When the server gets unavailable, the proccesses on the client will lock > - OK so far. > The problematic thing is, after the server is back online, I still see no > way to get the locked processes back to continue. They are still in heir > NFS-lock. All I can do is reboot the system. That only happens when I > mount the nfs filesystem with "soft". > > olivleh1@kartoffel olivleh1> ps auxww | grep bee > olivleh1 633 0.0 0.9 70980 18668 v0 S Wed10PM 14:19.21 beep- > media-player > > When I don't use that option, it continues playing after the server is > back online. > > > -- > Oliver Lehmann > http://www.pofo.de/ > http://wishlist.ans-netz.de/ > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050708215444.50691.qmail>