Re: [nfsv4] What error to return if destination server fails to READ within cnr_lease_time
Tom Haynes <thomas.haynes@primarydata.com> Fri, 18 December 2015 20:38 UTC
Return-Path: <thomas.haynes@primarydata.com>
X-Original-To: nfsv4@ietfa.amsl.com
Delivered-To: nfsv4@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 491A31B38C3 for <nfsv4@ietfa.amsl.com>; Fri, 18 Dec 2015 12:38:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 LR5TsCLFjMdd for <nfsv4@ietfa.amsl.com>; Fri, 18 Dec 2015 12:38:07 -0800 (PST)
Received: from mail-pa0-x22a.google.com (mail-pa0-x22a.google.com [IPv6:2607:f8b0:400e:c03::22a]) (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 8779F1B38C1 for <nfsv4@ietf.org>; Fri, 18 Dec 2015 12:38:07 -0800 (PST)
Received: by mail-pa0-x22a.google.com with SMTP id q3so45431023pav.3 for <nfsv4@ietf.org>; Fri, 18 Dec 2015 12:38:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=primarydata-com.20150623.gappssmtp.com; s=20150623; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=NXK0yH26BiDwUct33T0boPNd9NxTOUQ4PDcUqBhxnxY=; b=LuiosHwU2su8kzgQRmCIsqm6NFTfpeSEzmZcQVGXm2JR4slTg6wDnagV9DP5PJTxnP GpW9l+Bbw/gnRenKXIhodkjcgOGJDPWAj4kDzng1WwJc3z11rL3xJY5JB2I2gmFh7vql lIFHGChoX9659S+lENaM9nGYFgCbbc0IKoQFDbBDuq3A8BJcUzCbYQXrCba2Gd85Wmqn ZCQHYt1EH/mCFAoNjm15t5EM46cBx1ThuMeJXccBJ4fVwTSw+fg2jK7Pg3QuEf0gPgwF KX147eMZuGRatN1CLvWRh8rycmaYYwGb+O9+vSSUvBprBoCCt0W+vk4DQB4lfNA0UrT/ hjKg==
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:message-id:references:to; bh=NXK0yH26BiDwUct33T0boPNd9NxTOUQ4PDcUqBhxnxY=; b=gZWrMjmpqdiDBmGYYqRE/4ZwnQL5qEbG4TzZJWyJQXqVgT5jHrI8IZd7vsRWEs2sEv beeIy90qf573HBUtJQGeO2b2IuleWFPfTyULkQNuf4rByV2T34RxPNkosJTEOnL1PvQG Be1W0x4VmSrh5V9Qc+dbdGoPDn0sn9VEzJfB7qImYPHh7aZXGcyVoaDBKfM/bO8Kokfj PYjaVLOldk+wQ+ddxvaoVP8+svUW9dxVIGKglck56FJkKfcNuXaUzgzOEoWafaLvr9vy r91MyHLK8ZXncuizIq+J6s0IZYw+NCU7zPDN+G+351YKtxaxb2FqWaxrKOmy99elUuhX UE/Q==
X-Gm-Message-State: ALoCoQkbQgTE+EbKs1Sm7My7UUTQAYjoS0HPu1GyL+ILEYotWlQVkmE7W/Dh0M6zi6kVitMF/f/QPmmGht0qz5DfGoTVJ061Tg==
X-Received: by 10.66.131.45 with SMTP id oj13mr8104224pab.147.1450471087187; Fri, 18 Dec 2015 12:38:07 -0800 (PST)
Received: from kinslayer.corp.primarydata.com (63-157-6-18.dia.static.qwest.net. [63.157.6.18]) by smtp.gmail.com with ESMTPSA id 7sm6487829pfn.83.2015.12.18.12.36.10 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 18 Dec 2015 12:36:27 -0800 (PST)
Content-Type: multipart/alternative; boundary="Apple-Mail=_F60AB8F5-5959-4F4A-9C47-29523993B3F7"
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
From: Tom Haynes <thomas.haynes@primarydata.com>
In-Reply-To: <601F497C-40CF-409E-A2C3-561234AC54B9@netapp.com>
Date: Fri, 18 Dec 2015 12:36:10 -0800
Message-Id: <225A3A7C-0818-4E25-AE1A-0DE819054301@primarydata.com>
References: <2EE02221-E9C5-4087-AFA6-1A1D52308C0C@netapp.com> <CADaq8jfxrJDvtfhEVeGMXkD4PLFcv5sfBP4g4B6VUfdhB_Ks2w@mail.gmail.com> <E19898F5-E239-42D8-87FE-870712D5DA63@netapp.com> <CADaq8jePDoEj=jt2pC5_ko+8wiX4d7EVO-EDKPmPJTNqthhFKg@mail.gmail.com> <601F497C-40CF-409E-A2C3-561234AC54B9@netapp.com>
To: "Adamson, Andy" <William.Adamson@netapp.com>
X-Mailer: Apple Mail (2.3112)
Archived-At: <http://mailarchive.ietf.org/arch/msg/nfsv4/mp9XRf9WSrN84ZBuwaUynXHfDrw>
Cc: NFSv4 <nfsv4@ietf.org>
Subject: Re: [nfsv4] What error to return if destination server fails to READ within cnr_lease_time
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.15
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, 18 Dec 2015 20:38:09 -0000
> On Dec 18, 2015, at 11:09 AM, Adamson, Andy <William.Adamson@netapp.com> wrote: >> > > All of the above complexity goes away if a READ for the COPY is able to return NFS4ERR_PARTNER_NO_AUTH. > My only concern here is that if a COPY in not going on and a client gets NFS4ERR_PARTNER_NO_AUTH, what is it supposed to do with the error? My proposal is that we simply treat that as NFS4ERR_SERVERFAULT. Objections? I’ll post a patch soon for all of this.
- [nfsv4] What error to return if destination serve… Adamson, Andy
- Re: [nfsv4] What error to return if destination s… David Noveck
- Re: [nfsv4] What error to return if destination s… Adamson, Andy
- Re: [nfsv4] What error to return if destination s… David Noveck
- Re: [nfsv4] What error to return if destination s… Adamson, Andy
- Re: [nfsv4] What error to return if destination s… Tom Haynes
- Re: [nfsv4] What error to return if destination s… Tom Haynes
- Re: [nfsv4] What error to return if destination s… David Noveck