From owner-freebsd-fs@freebsd.org Tue Jul 28 12:47:57 2015 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8E6029AC314 for ; Tue, 28 Jul 2015 12:47:57 +0000 (UTC) (envelope-from email.ahmedkamal@googlemail.com) Received: from mail-wi0-x236.google.com (mail-wi0-x236.google.com [IPv6:2a00:1450:400c:c05::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 22C001EB9 for ; Tue, 28 Jul 2015 12:47:57 +0000 (UTC) (envelope-from email.ahmedkamal@googlemail.com) Received: by wibxm9 with SMTP id xm9so155641678wib.0 for ; Tue, 28 Jul 2015 05:47:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=fSDIOCU/ZeAS4Jb56Uz1INqDsHOpWRd0UdCDXteZdYg=; b=X8hqY3VIsaPCF4B1P0rWr6CL7iSFSP92v7ECAUrx7zgIBa+tH8nw4+N0b1Z7KhgEXj ZC2b5pQ0HWXJrE7xAr57dI3RwfxO00+A3Ag6m60kgWKnpOGbr5iLxifzF4FDjk/vSSo8 eWn3V1rc7/pZ7ow7O3n2DhxqKGni0O8NR6f4zs8AiT4XtAIQPP1U7B4BsrygARuJulee 6hShyzMUdOMrJF5pjkszHNOWG8tQ6s+HNRWhxRAwrBWbUkTUsaTVuSsEILeilY/b6j7e qesBOpmIbPepCu/8cRb4ymlHO27Nj+MFlRul+WhJff0t5A+S9UDoAh6CXAIDYLRmFFbn ABxQ== X-Received: by 10.194.236.161 with SMTP id uv1mr69726713wjc.158.1438087675435; Tue, 28 Jul 2015 05:47:55 -0700 (PDT) MIME-Version: 1.0 Received: by 10.28.6.143 with HTTP; Tue, 28 Jul 2015 05:47:35 -0700 (PDT) In-Reply-To: <576106597.2326662.1437688749018.JavaMail.zimbra@uoguelph.ca> References: <684628776.2772174.1435793776748.JavaMail.zimbra@uoguelph.ca> <20150716235022.GF32479@physics.umn.edu> <184170291.10949389.1437161519387.JavaMail.zimbra@uoguelph.ca> <55B12EB7.6030607@physics.umn.edu> <1935759160.2320694.1437688383362.JavaMail.zimbra@uoguelph.ca> <576106597.2326662.1437688749018.JavaMail.zimbra@uoguelph.ca> From: Ahmed Kamal Date: Tue, 28 Jul 2015 14:47:35 +0200 Message-ID: Subject: Re: Linux NFSv4 clients are getting (bad sequence-id error!) To: Rick Macklem Cc: Graham Allan , Ahmed Kamal via freebsd-fs Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jul 2015 12:47:57 -0000 Hi again Rick, Seems that I'm still being unlucky with nfs :/ I caught one of the newly installed RHEL6 boxes having high CPU usage, and bombarding the BSD NFS box with 10Mbps traffic .. I caught a tcpdump as you mentioned .. You can download it here: https://dl.dropboxusercontent.com/u/51939288/nfs41-high-client-cpu.pcap.bz2 I didn't restart the client yet .. so if you catch me in the next few hours and want me to run any diagnostics, let me know. Thanks a lot all for helping On Thu, Jul 23, 2015 at 11:59 PM, Rick Macklem wrote: > Ahmed Kamal wrote: > > Can you please let me know the ultimate packet trace command I'd need to > > run in case of any nfs4 troubles .. I guess this should be comprehensive > > even at the expense of a larger output size (which we can trim later).. > > Thanks a lot for the help! > > > tcpdump -s 0 -w .pcap host > ( refers to a file name you choose and refers to > the host name of a client generating traffic.) > --> But you won't be able to allow this to run for long during the storm > or the > file will be huge. > > Then you look at .pcap in wireshark, which knows NFS. > > rick > > > On Thu, Jul 23, 2015 at 11:53 PM, Rick Macklem > wrote: > > > > > Graham Allan wrote: > > > > For our part, the user whose code triggered the pathological > behaviour > > > > on SL5 reran it on SL6 without incident - I still see lots of > > > > sequence-id errors in the logs, but nothing bad happened. > > > > > > > > I'd still like to ask them to rerun again on SL5 to see if the > "accept > > > > skipped seqid" patch had any effect, though I think we expect not. > Maybe > > > > it would be nice if I could get set up to capture rolling tcpdumps of > > > > the nfs traffic before they run that though... > > > > > > > > Graham > > > > > > > > On 7/20/2015 10:26 PM, Ahmed Kamal wrote: > > > > > Hi folks, > > > > > > > > > > I've upgraded a test client to rhel6 today, and I'll keep an eye > on it > > > > > to see what happens. > > > > > > > > > > During the process, I made the (I guess mistake) of zfs send | > recv to > > > a > > > > > locally attached usb disk for backup purposes .. long story short, > > > > > sharenfs property on the received filesystem was causing some > > > nfs/mountd > > > > > errors in logs .. I wasn't too happy with what I got .. I > destroyed the > > > > > backup datasets and the whole pool eventually .. and then rebooted > the > > > > > whole nas box .. After reboot my logs are still flooded with > > > > > > > > > > Jul 21 05:12:36 nas kernel: nfsrv_cache_session: no session > > > > > Jul 21 05:13:07 nas last message repeated 7536 times > > > > > Jul 21 05:15:08 nas last message repeated 29664 times > > > > > > > > > > Not sure what that means .. or how it can be stopped .. Anyway, > will > > > > > keep you posted on progress. > > > > > > > Oh, I didn't see the part about "reboot" before. Unfortunately, it > sounds > > > like the > > > client isn't recovering after the session is lost. When the server > > > reboots, the > > > client(s) will get NFS4ERR_BAD_SESSION errors back because the server > > > reboot has > > > deleted all sessions. The NFS4ERR_BAD_SESSION should trigger state > > > recovery on the client. > > > (It doesn't sound like the clients went into recovery, starting with a > > > Create_session > > > operation, but without a packet trace, I can't be sure?) > > > > > > rick > > > > > > > > > > > -- > > > > > ------------------------------------------------------------------------- > > > > Graham Allan - gta@umn.edu - allan@physics.umn.edu > > > > School of Physics and Astronomy - University of Minnesota > > > > > ------------------------------------------------------------------------- > > > > > > > > > > > > > >