Date: Fri, 08 Jul 2005 15:49:39 -0700 From: Yu-Shun Wang <yushunwa@ISI.EDU> To: Mohan Srinivasan <mohan_srinivasan@yahoo.com> Cc: freebsd-current@freebsd.org, Oliver Lehmann <lehmann@ans-netz.de>, Claus Guttesen <kometen@gmail.com> Subject: Re: problems with soft-nfs when the server goes down Message-ID: <42CF0303.3090004@isi.edu> In-Reply-To: <20050708213919.15818.qmail@web80604.mail.yahoo.com> References: <20050708213919.15818.qmail@web80604.mail.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] Mohan Srinivasan wrote: > --- Claus Guttesen <kometen@gmail.com> wrote: >>>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". >> >>Do you tcp- or udp-mount? AFAIK tcp-mount's don't work properly in 6.0 >>(current). > NFS/TCP mounts should work in -current. There was a bug reported > against NFS/TCP (retransmits were not happening reliably when the > server went down). That was fixed several weeks ago. > > If you see something broken with NFS/TCP, please let me know. Hi, I am not sure that's the case. We might be talking about differnt bugs FWIW. I also had NFS-related lockups as recent as CURRENT on 6/27/2005, probably on 7/5/2005 as well. You could search for 'nfs' on the list for the last two months. As far as I could remember, the problem has to do with nfs pkts or mbuf mis-alignment, and the realign functions in either the client or the server couldn't deal with serious mis-alignment. I could be wrong, check the archive for more details. Just a data point of my setup: nfs client running CURRENT, server is solaris, was using NFS/TCP with NFSv3. Simple TCPDUMP showed that the client kept sending access request and the server kept answering it, but the client never accepted (for the lack of better terms) those replies. So in my case, the server was never down (at least during those lockups). I have no hard evidence on how to re-produce the lockups, some mentioned after or duing heavy IO traffic. But it's definitely there. It annoyed me enough that I took the easy way out: switched to NFS/UDP since yesterday. :-) Thanks, yushun -- Yu-Shun Wang <yushunwa@isi.edu> http://www.isi.edu/~yushunwa USC Information Sciences Institute [-- Attachment #2 --] 0 *H 010 + 0 *H y00 0 *H 0b10 UZA1%0#U Thawte Consulting (Pty) Ltd.1,0*U#Thawte Personal Freemail Issuing CA0 050215222044Z 060215222044Z0z1 0UWang10U*Yu-Shun10UYu-Shun Wang10 *H yushunwa@isi.edu10 *H yushunwa@usc.edu0"0 *H 0 o4'ܝ416 liIw*3 p\ Fjs]3|J$蒨LtYDH>gX`VjzK)j@k|*[2PU3ߴ1zȲ@ mK-g 1ۍtJ ٗF6qJ_ltmU@ۓwGӇómJq,Ӧ,dF≑~Z*5҄rm ?0=0-U&0$yushunwa@isi.eduyushunwa@usc.edu0U0 0 *H c})>X0d%j6Ǧ}G &Ņ;rj=Fw3Cu}в^_AQXc龭N'hU@ZEO.00 0 *H 0b10 UZA1%0#U Thawte Consulting (Pty) Ltd.1,0*U#Thawte Personal Freemail Issuing CA0 050215222044Z 060215222044Z0z1 0UWang10U*Yu-Shun10UYu-Shun Wang10 *H yushunwa@isi.edu10 *H yushunwa@usc.edu0"0 *H 0 o4'ܝ416 liIw*3 p\ Fjs]3|J$蒨LtYDH>gX`VjzK)j@k|*[2PU3ߴ1zȲ@ mK-g 1ۍtJ ٗF6qJ_ltmU@ۓwGӇómJq,Ӧ,dF≑~Z*5҄rm ?0=0-U&0$yushunwa@isi.eduyushunwa@usc.edu0U0 0 *H c})>X0d%j6Ǧ}G &Ņ;rj=Fw3Cu}в^_AQXc龭N'hU@ZEO.0?0 0 *H 010 UZA10UWestern Cape10U Cape Town10U Thawte Consulting1(0&UCertification Services Division1$0"UThawte Personal Freemail CA1+0) *H personal-freemail@thawte.com0 030717000000Z 130716235959Z0b10 UZA1%0#U Thawte Consulting (Pty) Ltd.1,0*U#Thawte Personal Freemail Issuing CA00 *H 0 Ħ<UsUNʙZhup[v:aQP 0cZ,p+Z?qV˯<6$*+w=+>@dקe*TH<a@dr` 00U0 0CU<0:08642http://crl.thawte.com/ThawtePersonalFreemailCA.crl0U0)U"0 010UPrivateLabel2-1380 *H HP. fgCL!6-6/P p<ab:~ t%Pb'qW%ݩ9 Oe_N4[5MwV!x!5$F]_eO1;070i0b10 UZA1%0#U Thawte Consulting (Pty) Ltd.1,0*U#Thawte Personal Freemail Issuing CA 0 + 0 *H 1 *H 0 *H 1 050708224939Z0# *H 1|6佘txhv0R *H 1E0C0 *H 0*H 0 *H @0+0 *H (0x +71k0i0b10 UZA1%0#U Thawte Consulting (Pty) Ltd.1,0*U#Thawte Personal Freemail Issuing CA 0z*H 1ki0b10 UZA1%0#U Thawte Consulting (Pty) Ltd.1,0*U#Thawte Personal Freemail Issuing CA 0 *H k*k:"Ғdb L;hQ^W~ou\J\Gt9T+[ 6zAD tNsR|$M~,iY/_JsĮ3*v% KE5(uBWʋ^+WgrV$jnSQ1u6>vy&;I/ID+249 folx.F4h+":V}Jm\
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?42CF0303.3090004>
