Re: [nfsv4] FYI: Readdir not allowed on NFS pseudo root

Stevan Steve Allen <scallen@us.ibm.com> Sun, 16 May 2004 04:46 UTC

Received: from optimus.ietf.org (iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA28795 for <nfsv4-archive@odin.ietf.org>; Sun, 16 May 2004 00:46:31 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BPDWR-0001I3-1l for nfsv4-archive@odin.ietf.org; Sun, 16 May 2004 00:45:11 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i4G4jBLN004959 for nfsv4-archive@odin.ietf.org; Sun, 16 May 2004 00:45:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BPDUv-00011a-Pv for nfsv4-web-archive@optimus.ietf.org; Sun, 16 May 2004 00:43:37 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA28725 for <nfsv4-web-archive@ietf.org>; Sun, 16 May 2004 00:43:34 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BPDUt-0004Ak-6d for nfsv4-web-archive@ietf.org; Sun, 16 May 2004 00:43:35 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BPDTv-0003o3-00 for nfsv4-web-archive@ietf.org; Sun, 16 May 2004 00:42:36 -0400
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BPDTP-0003RI-00 for nfsv4-web-archive@ietf.org; Sun, 16 May 2004 00:42:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BPDKi-0008EI-8d; Sun, 16 May 2004 00:33:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BPDDa-0007Ej-HE for nfsv4@optimus.ietf.org; Sun, 16 May 2004 00:25:42 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA28211 for <nfsv4@ietf.org>; Sun, 16 May 2004 00:25:39 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BPDDY-0004yX-0p for nfsv4@ietf.org; Sun, 16 May 2004 00:25:40 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BPDCf-0004Yo-00 for nfsv4@ietf.org; Sun, 16 May 2004 00:24:46 -0400
Received: from e32.co.us.ibm.com ([32.97.110.130]) by ietf-mx with esmtp (Exim 4.12) id 1BPDBk-0003iO-00 for nfsv4@ietf.org; Sun, 16 May 2004 00:23:48 -0400
Received: from westrelay02.boulder.ibm.com (westrelay02.boulder.ibm.com [9.17.195.11]) by e32.co.us.ibm.com (8.12.10/8.12.2) with ESMTP id i4G4NIBM501310; Sun, 16 May 2004 00:23:18 -0400
Received: from d03nm113.boulder.ibm.com (d03av04.boulder.ibm.com [9.17.195.170]) by westrelay02.boulder.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id i4G4NHOD379454; Sat, 15 May 2004 22:23:18 -0600
In-Reply-To: <6F678A66-A6B6-11D8-A312-000A95DBCB70@sun.com>
To: Spencer Shepler <spencer.shepler@sun.com>
Cc: nfsv4@ietf.org
MIME-Version: 1.0
Subject: Re: [nfsv4] FYI: Readdir not allowed on NFS pseudo root
X-Mailer: Lotus Notes Release 6.0.2CF1 June 9, 2003
Message-ID: <OF2B709EA2.791AD6CB-ON87256E96.0005DBB2-88256E96.0017B32B@us.ibm.com>
From: Stevan Steve Allen <scallen@us.ibm.com>
X-MIMETrack: Serialize by Router on D03NM113/03/M/IBM(Release 6.0.2CF2HF259 | March 11, 2004) at 05/15/2004 22:23:18, Serialize complete at 05/15/2004 22:23:18
Content-Type: multipart/alternative; boundary="=_alternative 0017B32288256E96_="
Sender: nfsv4-admin@ietf.org
Errors-To: nfsv4-admin@ietf.org
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=unsubscribe>
List-Id: NFSv4 Working Group <nfsv4.ietf.org>
List-Post: <mailto:nfsv4@ietf.org>
List-Help: <mailto:nfsv4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/mail-archive/working-groups/nfsv4/>
X-Original-Date: Sat, 15 May 2004 21:18:53 -0700
Date: Sat, 15 May 2004 21:18:53 -0700
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL, HTML_MESSAGE autolearn=no version=2.60

Spencer, my intro to Open Systems is still somewhat limited.  Without 
mount support in v4, are you inquiring about Mount in general? 

The operating system is IBM z/OS which contains a flat filesystem with a 
UNIX layer.  The z/OS NFSv3 server will access files directly (filesysA) 
or through the UNIX layer (filesysB).

Basically, z/OS NFSv3 represents two unconnected filesystems where NFSv4 
has introduced a connecting root.

The flat file system is represented by qualified filenames such as 
USER.PROJECTS.NFS.ATTR.  A problem for z/OS NFSv3 is a READDIR of the flat 
filesystem root represents every file in the system.  This is not 
permitted by the z/OS catalog facility due to the output size. 

To address the z/OS 'list all' restriction, z/OS mount support REQUIRES a 
mount on a filename prefix or UNIX directory.  NFSv3 converts flat 
filenames to a hierarchical directory structure.  A mount location may be 
USER or NFS.EXPORTED or /HFS/u/pub allowing a READDIR from this point on. 

The current plan is to return NFS4ERR_NOENT for a READDIR of the NFSv4 
pseudo root.  e.g. the pseudo root will take on the current restrictions 
of the flat filesys root. 

z/OS NFSv3 Pubs:
http://www.ibm.com/servers/eserver/zseries/zos/zos_elefeat.html#n 


On May 15, 2004, at 10:26 AM, Stevan Steve Allen wrote:

>
> FYI:
>
> Our NFS server sits on top of two operating systems, one UNIX and one 
> non hierarchical.  An OS restriction in this environment is READDIR is 
> not allowed from the new NFS pseudo root.  Lookup will be allowed.  
>
> A GETATTR for our NFS pseudo root will return a mode with execute 
> permission bits on to permit change dir, all read and write mode bits 
> are off.

Would you be able to be more specific about the operating
environments for which this server will be available?  This will
allow the client implementors to be able to respond to user
questions about things not working when the client mounts / from
the server.

Spencer