From owner-freebsd-stable@FreeBSD.ORG Sat May 23 20:24:41 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6BC1BB26 for ; Sat, 23 May 2015 20:24:41 +0000 (UTC) Received: from mail-ig0-x22a.google.com (mail-ig0-x22a.google.com [IPv6:2607:f8b0:4001:c05::22a]) (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 356C919F7 for ; Sat, 23 May 2015 20:24:41 +0000 (UTC) Received: by igbpi8 with SMTP id pi8so14541467igb.0 for ; Sat, 23 May 2015 13:24:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=neosmart.net; s=google; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=l4rZcTcHpkU9PIPCs+LbvNrndio73HAqdvyWc2LpXcE=; b=KF5vlQ/MlmwLRbaoPP8WDTwgycoXl8mcGjRcfUm+feSC4T1xP5VHExZ8yF34Awwdm9 A1tLPhJEG20SBPWUgB3Y5g3iYqEBLGlmfCz7aA8THqQLxsU2wNRCSKaH0eT+mz62JGjT 62oBvzgvpnj6TkcEiAIO2KucB2zYdUvnIssS4= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=l4rZcTcHpkU9PIPCs+LbvNrndio73HAqdvyWc2LpXcE=; b=PTvdKJn9WCjrON4y9YRXIgoCciuGaaBl2W2HCCNdlDYsabs3D9k0yCaJjFQlPzP53L eGJzECi2TI6v0kIIW18Mm+Yx7JuqGvp2hcsKa6YwDkr173wJCWK4Xa4e2Xv9V6CmuT3y kpat6tY+Ad2FkiTSimD60E1YtG8UkP1CRTS609Pl+8iphPAEeESbG4bF3pq8ZVGtDG9Z jqg0Q7fVYeXDraJt6APAHDD/Pdayg2I1dNNIB6gtvL5ATsouVxHQcMbUB+1Qe2ehrwi0 lQj7d4Pc+eeN2VJ/VysiPJNeAS/yIW28GqR2PowUNC3dTx2CUQG8YVgdhnDY56DTWbtX c8UA== X-Gm-Message-State: ALoCoQmm09VERkAE8j+V0ehQQVbg+xRCRk103ftecqYQTzGzCwwJPe0VrTM2eBQGK87K0YDSNpij X-Received: by 10.50.90.179 with SMTP id bx19mr13758742igb.43.1432412680503; Sat, 23 May 2015 13:24:40 -0700 (PDT) Received: from [192.168.2.30] (ERMLON6511W-LP140-03-3096583261.dsl.bell.ca. [184.146.28.93]) by mx.google.com with ESMTPSA id o9sm4899651ioe.35.2015.05.23.13.24.39 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 23 May 2015 13:24:40 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2100\)) Subject: Re: Status of NFS4.1 FS_RECLAIM in FreeBSD 10.1? From: Mahmoud Al-Qudsi In-Reply-To: <1950364073.41930419.1432210777686.JavaMail.root@uoguelph.ca> Date: Sat, 23 May 2015 16:24:38 -0400 Cc: freebsd-stable@freebsd.org Content-Transfer-Encoding: 7bit Message-Id: References: <1950364073.41930419.1432210777686.JavaMail.root@uoguelph.ca> To: Rick Macklem X-Mailer: Apple Mail (2.2100) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 May 2015 20:24:41 -0000 > On May 21, 2015, at 8:19 AM, Rick Macklem wrote: > > Well, if you are just doing an NFSv4.1 mount, you could capture > packets during the failed mount attaempt with tcpdump and then > email me the raw packet capture, I can take a look at it. > (tcpdump doesn't handle nfs packets well, but wireshark will accept > a raw packet capture) Something like: > # tcpdump -s 0 -w .pcap host > should work. > > When I read RFC-5661 around page #567, it seems clear that the > client should use RECLAIM_COMPLETE with the fs arg false after > acquiring a noew clientid, which is what a fresh mount would normally be. > (If the packet capture shows an EXCHANGEID followed by a RECLAIM_COMPLETE > with the fs arg true, I think ESXi is broken, but I can send you a patch > that will just ignore the "true", so it works.) > I think the "true" case is only used when a file system has been "moved" > by a server cluster, indicated to the client via a NFS4ERR_MOVED error > when it is accessed at the old server, but the working in RFC-5661 isn't > very clear. > > rick Thank you kindly. I am travelling at the moment; but as soon as I can, I will get that to you. Much appreciated, Mahmoud