IETF Logo Mail Archive

Re: [nfsv4] RFC 7530: Available attributes for READDIR and Absent File Systems

Marcel Telka <marcel@telka.sk> Mon, 22 May 2017 12:45 UTC

Return-Path: <marcel@telka.sk>
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 0C02112D574 for <nfsv4@ietfa.amsl.com>; Mon, 22 May 2017 05:45:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.8
X-Spam-Level:
X-Spam-Status: No, score=0.8 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 AhIKWh3u9GL1 for <nfsv4@ietfa.amsl.com>; Mon, 22 May 2017 05:45:24 -0700 (PDT)
Received: from tortuga.telka.sk (tortuga.telka.sk [185.14.234.118]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 782A81293FD for <nfsv4@ietf.org>; Mon, 22 May 2017 05:45:23 -0700 (PDT)
Received: (qmail 19406 invoked from network); 22 May 2017 12:45:20 -0000
Received: from localhost (HELO tortuga.telka.sk) (127.0.0.1) by localhost with SMTP; 22 May 2017 12:45:20 -0000
Received: from spreva.in.telka.sk (spreva.in.telka.sk [10.0.0.11]) by mail.telka.sk (Horde Framework) with HTTPS; Mon, 22 May 2017 12:45:20 +0000
Date: Mon, 22 May 2017 12:45:20 +0000
Message-ID: <20170522124520.Horde.rD2-xzzGBFJBrqd049FsXNd@mail.telka.sk>
From: Marcel Telka <marcel@telka.sk>
To: nfsv4@ietf.org
References: <03970226-9CF0-4493-9408-F7CBC19F3919@gmail.com> <CADaq8jdttJ=2Ej-vsi6go2puPec5=pyf5aC60URaEgFzOA=daA@mail.gmail.com> <E8E85727-DF56-4BC4-9B1D-8BFC5139B5A1@gmail.com> <CADaq8jeYK8xPFb3kBUnSQ-2k=E53NfmJ6f6sBVTYifa6PXja7Q@mail.gmail.com>
In-Reply-To: <CADaq8jeYK8xPFb3kBUnSQ-2k=E53NfmJ6f6sBVTYifa6PXja7Q@mail.gmail.com>
User-Agent: Horde Application Framework 5
Content-Type: text/plain; charset="utf-8"; format="flowed"; DelSp="Yes"
MIME-Version: 1.0
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/XEzbVJ4DJCGpUOjZh6otuobIyLs>
Subject: Re: [nfsv4] RFC 7530: Available attributes for READDIR and Absent File Systems
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.22
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: Mon, 22 May 2017 12:45:26 -0000

Citát David Noveck <davenoveck@gmail.com>:
>> In other words, can other attributes than fs_locations, fsid,
> mounted_on_fileid, rdattr_error
>> be available for a root of absent filesystem in READDIR reply?
>
> According to the spec. yes.  Realistically, it is hard to come up with a
> case where the server would have this information or in which a client
> would be prepared to do anything with it.

One such example might be the filehandle attribute.  The server should  
have access to it and clients can use it for the subsequent GETATTR  
operation to get fs_locations, for example.


Thanks.

-- 
+-------------------------------------------+
| Marcel Telka   e-mail:   marcel@telka.sk  |
|                homepage: http://telka.sk/ |
|                jabber:   marcel@jabber.sk |
+-------------------------------------------+

v2.23.0 | Report a Bug | By Email