From owner-freebsd-stable@FreeBSD.ORG Fri Feb 22 15:34:18 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id A7408EA6 for ; Fri, 22 Feb 2013 15:34:18 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-annu.net.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id 6BAE7816 for ; Fri, 22 Feb 2013 15:34:18 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AqEEALyPJ1GDaFvO/2dsb2JhbABEDoZAulWBH3OCHwEBAQMBAQEBICsgCwUWDgoCAg0ZAikBCSYGCAcEARwEh2sGDK0FkjmBI4wqBgeBADQHgi2BEwOIaIsYgjqBHY9GgkhdT30BBxce X-IronPort-AV: E=Sophos;i="4.84,717,1355115600"; d="scan'208";a="15292328" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-annu.net.uoguelph.ca with ESMTP; 22 Feb 2013 10:33:47 -0500 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 108A6B3F19; Fri, 22 Feb 2013 10:33:47 -0500 (EST) Date: Fri, 22 Feb 2013 10:33:47 -0500 (EST) From: Rick Macklem To: Daniel Braniss Message-ID: <773493110.3210623.1361547227044.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: Subject: Re: zfs/nfs/proftpd problem MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.91.203] X-Mailer: Zimbra 6.0.10_GA_2692 (ZimbraWebClient - FF3.0 (Win)/6.0.10_GA_2692) Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Feb 2013 15:34:18 -0000 Daniel Braniss wrote: > after upgrading the 'ftp storage' from 8.3 to 9.1-stable, our ftp > server is stuck. > > the old, (ProFTPD Version 1.3.2) and working till before the upgrade > is stuck > in nlmrcv: > ... > 10000 1213 992 0 44 0 7340 3692 nlmrcv D ?? 0:08.07 proftpd: > ftp - > crawl-66-249-73-193.googlebot.com: anonymous/googlebot@google.com: > RETR 00690145.JPG (proftpd) > ... > I suspect you know that this is waiting for a reply from some rpc.lockd. > so we upgraded the ftp server too, to 9.1/ProFTPD Version 1.3.4b and > this one > is stuck in rpccwnd: > 10000 1197 984 0 20 0 32292 4792 rpccwnd D ?? 0:00.01 proftpd: ftp > - > mbpro.cs.huji.ac.il: anonymous/mozilla@example.com: LIST (proftpd) > This one is stuck in the client side of UDP for the krpc, in the primitive congestion control stuff that is there. > > any wise suggestions :-) > Well, maybe not wise, but you may already be aware that NFS etc over UDP and the NLM are two of my favourite things (especially the NLM). Basically, it appears to be having difficulties doing RPCs over UDP, at least for the NLM (rpc.lockd), suggesting some transport related issue. First, make sure rpc.statd and rpc.lockd are running on the NFS server and all clients (or disable use of it via the "nolockd" mount option). You can also do a "netstat -s" and see if there is a non-zero count for "fragments dropped due to timeout" in the IP section. (This happens when your network fabric can't handle the burst of IP fragments generated by a large RPC message over UDP.) Things you could try: - If you are using a udp mount for NFS... - reduce your rsize and wsize (especially if "fragments dropped due to timeout" is non-zero) or - switch to TCP If you are not using udp mounts, then the NLM (rpc.lockd) is using UDP anyhow. If you don't need multiple NFS clients to see the file locks, add "nolockd" to your mount(s). Beyond that, you'll need to capture packets and look at them in wireshark, to see what is going on. Good luck with it, rick > cheers, > danny > > > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to > "freebsd-stable-unsubscribe@freebsd.org"