From owner-freebsd-current@FreeBSD.ORG Fri Jul 8 21:54:45 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2F6E016A41C for ; Fri, 8 Jul 2005 21:54:45 +0000 (GMT) (envelope-from mohan_srinivasan@yahoo.com) Received: from web80602.mail.yahoo.com (web80602.mail.yahoo.com [66.218.79.91]) by mx1.FreeBSD.org (Postfix) with SMTP id E798543D5C for ; Fri, 8 Jul 2005 21:54:44 +0000 (GMT) (envelope-from mohan_srinivasan@yahoo.com) Received: (qmail 50693 invoked by uid 60001); 8 Jul 2005 21:54:44 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=CstjrqLqb9jA6QU4qNN3UKEOXlqCWpYP10Pzd45U79W/VheTsd1BeMnYgSW0iYz0YMtbysGpIcoHdVN0UXBdAYgxm1ap6kssfDGa1LcIw7+osPghrvRoj9h+0EQcUkG8+gL8Zy4S2t80ir8f+0TNho9UXqSXlFQUxg77fRBQhrs= ; Message-ID: <20050708215444.50691.qmail@web80602.mail.yahoo.com> Received: from [207.126.239.39] by web80602.mail.yahoo.com via HTTP; Fri, 08 Jul 2005 14:54:44 PDT Date: Fri, 8 Jul 2005 14:54:44 -0700 (PDT) From: Mohan Srinivasan To: Oliver Lehmann , freebsd-current@freebsd.org In-Reply-To: <20050708222246.630c9de3.lehmann@ans-netz.de> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: Subject: Re: problems with soft-nfs when the server goes down X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jul 2005 21:54:45 -0000 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 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" >