Re: [nfsv4] [PATCH 2/3] Morph LAYOUTRETURN errors into LAYOUTERROR

Christoph Hellwig <hch@lst.de> Fri, 16 May 2014 08:23 UTC

Return-Path: <hch@lst.de>
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 8F94F1A018D for <nfsv4@ietfa.amsl.com>; Fri, 16 May 2014 01:23:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.201
X-Spam-Level:
X-Spam-Status: No, score=-2.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RP_MATCHES_RCVD=-0.651] 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 IbKK6Mv_tp-z for <nfsv4@ietfa.amsl.com>; Fri, 16 May 2014 01:23:36 -0700 (PDT)
Received: from newverein.lst.de (verein.lst.de [213.95.11.211]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6E2E21A0133 for <nfsv4@ietf.org>; Fri, 16 May 2014 01:23:36 -0700 (PDT)
Received: by newverein.lst.de (Postfix, from userid 2407) id 2959D13F0A; Fri, 16 May 2014 10:23:28 +0200 (CEST)
Date: Fri, 16 May 2014 10:23:28 +0200
From: Christoph Hellwig <hch@lst.de>
To: Thomas Haynes <thomas.haynes@primarydata.com>
Message-ID: <20140516082328.GB25772@lst.de>
References: <1400201769-40352-1-git-send-email-Thomas.Haynes@primarydata.com> <1400201769-40352-3-git-send-email-Thomas.Haynes@primarydata.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <1400201769-40352-3-git-send-email-Thomas.Haynes@primarydata.com>
User-Agent: Mutt/1.5.17 (2007-11-01)
Archived-At: http://mailarchive.ietf.org/arch/msg/nfsv4/AvYzwcPYUfLm8njnF5aJbuvb7s4
Cc: nfsv4@ietf.org
Subject: Re: [nfsv4] [PATCH 2/3] Morph LAYOUTRETURN errors into LAYOUTERROR
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: <http://www.ietf.org/mail-archive/web/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, 16 May 2014 08:23:37 -0000

> +    <t>
> +      Each individual device_error4 describes a single error
> +      associated with a storage device, which is identified via
> +      de_deviceid.  The operation which returned the error is
> +      identified via de_opnum. Finally the NFS error value (nfsstat4)
> +      encountered is provided via de_status and may consist of the
> +      following error codes:

What would the client put into de_opnum for block or object layouts?