From owner-freebsd-fs@freebsd.org Thu Jul 23 18:13:24 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 7E2DC9A914A for ; Thu, 23 Jul 2015 18:13:24 +0000 (UTC) (envelope-from allan@physics.umn.edu) Received: from mail.physics.umn.edu (smtp.spa.umn.edu [128.101.220.4]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 59A101256 for ; Thu, 23 Jul 2015 18:13:22 +0000 (UTC) (envelope-from allan@physics.umn.edu) Received: from c-66-41-25-68.hsd1.mn.comcast.net ([66.41.25.68] helo=[192.168.0.2]) by mail.physics.umn.edu with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from ) id 1ZIKzc-0006O5-5H; Thu, 23 Jul 2015 13:13:16 -0500 Message-ID: <55B12EB7.6030607@physics.umn.edu> Date: Thu, 23 Jul 2015 13:13:11 -0500 From: Graham Allan User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: Ahmed Kamal , Rick Macklem CC: Ahmed Kamal via freebsd-fs Subject: Re: Linux NFSv4 clients are getting (bad sequence-id error!) References: <684628776.2772174.1435793776748.JavaMail.zimbra@uoguelph.ca> <5594B008.10202@freebsd.org> <1022558302.2863702.1435838360534.JavaMail.zimbra@uoguelph.ca> <791936587.3443190.1435873993955.JavaMail.zimbra@uoguelph.ca> <20150716235022.GF32479@physics.umn.edu> <184170291.10949389.1437161519387.JavaMail.zimbra@uoguelph.ca> In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit 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: Thu, 23 Jul 2015 18:13:24 -0000 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. -- ------------------------------------------------------------------------- Graham Allan - gta@umn.edu - allan@physics.umn.edu School of Physics and Astronomy - University of Minnesota -------------------------------------------------------------------------