IETF Logo Mail Archive

Re: [nfsv4] 4.0 trunking

Andy Adamson <androsadamson@gmail.com> Fri, 30 September 2016 20:25 UTC

Return-Path: <androsadamson@gmail.com>
X-Original-To: nfsv4@ietfa.amsl.com
Delivered-To: nfsv4@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E0DD12B181 for <nfsv4@ietfa.amsl.com>; Fri, 30 Sep 2016 13:25:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c7VrLq03y6Yq for <nfsv4@ietfa.amsl.com>; Fri, 30 Sep 2016 13:25:02 -0700 (PDT)
Received: from mail-it0-x241.google.com (mail-it0-x241.google.com [IPv6:2607:f8b0:4001:c0b::241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BA38812B025 for <nfsv4@ietf.org>; Fri, 30 Sep 2016 13:25:01 -0700 (PDT)
Received: by mail-it0-x241.google.com with SMTP id o19so2387210ito.3 for <nfsv4@ietf.org>; Fri, 30 Sep 2016 13:25:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=dAJXNmERHVdJtcNSzqSOvUxcOmao08XWm+NEaBhBrXI=; b=h0hrJ4kCnpKV6xjH2daQutQ9EjXjD6+NDRmahE8XLwvRJGuCsKsCO85isT2PquO308 B84KTGWX6EDeS7WLuwRaGQgfTI+EJgY1N/nv5Jp1xgvQoprZ3E9xiWVyPKlejYXAwMYQ I2kcqwp1unXGoH6L0b3oFg6mzSNXmxIIDpxuDMrPzau2Al5hMOTObMtjY+eSRkZt+eyr gau1JI5Gkh9Hz0Gouk22ks3g4aCNbhY9x1OpjUdgiPOaro9JlIxus5wrM9Me1pYKbhIb /Zt1MQIg5f4giQEMy0SwXP+qM7efP3vjGLUI7oVkLeXer32xe0ZRNhP+OQX/TjaBIGuG pwyw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=dAJXNmERHVdJtcNSzqSOvUxcOmao08XWm+NEaBhBrXI=; b=R9w0ZkgO3fIlwb2EEPq/sJhB+bVrSW2AifGcRo7tIe/LeMwV6nmbk42ORZPcImU6MK pWHpL7QKrkYlenB/Ie+WiWoDdmi+udjosfIm3HwpsOhs6PQPiaFulGgEyg11gP//80Px vAnNWyFrotqq98IimIobPqwAs+H1wVjHOBNFHBo1g3ZCrCyxJd/hMwaBk4I//QrGM2uE bCd38pX94KTswD/+iUmWPPwWIVJywnsIZ5pNr8SERVkDWKZ1kAC08It0vg62n5xuLdmt 0BShFH/UboAkzbcWUpfTK6Tta11nkkl3iinfdKcgtANhmAV/NSw6wCxdTaiXFROXiHUw T+ng==
X-Gm-Message-State: AA6/9RlFQLOOmL6kA+aKgg/NNI3diXcq+l1/LFGThhpg5tqDEGGRx9ynlhzLxys3LngbZqZMlXZaXf+aJKxs0A==
X-Received: by 10.107.29.130 with SMTP id d124mr10670664iod.61.1475267101111; Fri, 30 Sep 2016 13:25:01 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.79.34.78 with HTTP; Fri, 30 Sep 2016 13:25:00 -0700 (PDT)
In-Reply-To: <20160920213931.GC12789@fieldses.org>
References: <20160907212039.GA6847@fieldses.org> <CADaq8jfiRU7DTRYXGHZvMALAZWeRjhqcpo8Si3_diMt_5dNSMw@mail.gmail.com> <20160908010532.GA10658@fieldses.org> <CADaq8jcnananUPDHH4Vzhv93JTxZegsZLMCtZWFD-keHheKvHA@mail.gmail.com> <20160910200355.GA30688@fieldses.org> <BBB2EBDC-6F05-44C1-B45A-C84C24A9AD7F@netapp.com> <20160920213931.GC12789@fieldses.org>
From: Andy Adamson <androsadamson@gmail.com>
Date: Fri, 30 Sep 2016 16:25:00 -0400
Message-ID: <CAHVgHyVrOW6qVRzDXqwxjh4n3dy-Up+kcSpzuTQon+cR1o9iYA@mail.gmail.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/VKNZ1BLWaiLcxrQCYvZR8OPxHkE>
Cc: "Adamson, Andy" <William.Adamson@netapp.com>, "nfsv4@ietf.org" <nfsv4@ietf.org>
Subject: Re: [nfsv4] 4.0 trunking
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: NFSv4 Working Group <nfsv4.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/nfsv4/>
List-Post: <mailto:nfsv4@ietf.org>
List-Help: <mailto:nfsv4-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Sep 2016 20:25:04 -0000

Hi

Chuck Lever and I are writing the IETF spec describing the use of
fs_locations/fs_locations_info for client multipath discovery for
NFSv4.1 non-pNFS or MDS server trunking. Do you think we should bother
with the NFSv4.0 (clientID trunking) case?

-->Andy

On Tue, Sep 20, 2016 at 5:39 PM, J. Bruce Fields <bfields@fieldses.org> wrote:
> On Mon, Sep 12, 2016 at 12:59:05PM +0000, Adamson, Andy wrote:
>> IMHO we should not worry too much about NFSv4.0 trunking as NFSv4.1+ solves this issue. Trunking is simply one more reason to move from NFSv4.0 to NFSv4.1.
>
> I tend to agree, but since it got implemented an was causing a real bug,
> it was hard to ignore....
>
> After a patch (55b9df93ddd6 "NFSv4/v4.1: Verify the client owner id
> during trunking detection", if anyone cares) the damage seems restricted
> to the non-default "migration" case, making this less of a concern.
>

v2.23.0 | Report a Bug | By Email