From rsb@sac.sfbay.sun.com Fri Sep 18 15:51:41 2009 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n8IMpeav025452 for ; Fri, 18 Sep 2009 15:51:40 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n8IMpcaK014108; Fri, 18 Sep 2009 23:51:39 +0100 (BST) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KQ600K03VI28N00@nwk-avmta-2.sfbay.sun.com>; Fri, 18 Sep 2009 15:51:38 -0700 (PDT) Received: from dm-sfbay-02.sfbay.sun.com ([129.146.11.31]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KQ60094VVI267A0@nwk-avmta-2.sfbay.sun.com>; Fri, 18 Sep 2009 15:51:38 -0700 (PDT) Received: from sac.sfbay.sun.com (sac.SFBay.Sun.COM [129.146.226.132]) by dm-sfbay-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n8IMpbne022782; Fri, 18 Sep 2009 15:51:37 -0700 (PDT) Received: from sac.sfbay.sun.com (localhost [127.0.0.1]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n8IMpaHB025447; Fri, 18 Sep 2009 15:51:36 -0700 (PDT) Received: (from rsb@localhost) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8/Submit) id n8IMpamV025443; Fri, 18 Sep 2009 17:51:36 -0500 (CDT) Date: Fri, 18 Sep 2009 17:51:36 -0500 (CDT) From: Rich.Brown@sun.com Subject: NFS Referrals [PSARC/2009/502 FastTrack timeout 09/25/2009] To: PSARC-ext@sun.com Cc: nfs-referrals@sun.com Message-id: <200909182251.n8IMpamV025443@sac.sfbay.sun.com> Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 Status: RO Content-Length: 10316 I'm sponsoring this case for Rob Thurlow. This case proposes to add NFS Referral support to the Solaris client and server. Minor binding is requested. This times out on Friday, 25 September, 2009. Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI This information is Copyright 2009 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: NFS Referrals 1.2. Name of Document Author/Supplier: Author: Rob Thurlow 1.3 Date of This Document: 18 September, 2009 4. Technical Description NFS Referrals A. Introduction This project intends to introduce basic NFS referral support to the Solaris client and server. A Solaris client will follow a referral to a new location and transparently mount it, and a Solaris server will have basic support for creating and managing referrals. Referral support will permit construction of a server-based unified namespace that NFS clients will be able to participate in. NFSv4 referrals are supported by modern HP-UX, AIX, Linux releases. This project makes use of Reparse Points, PSARC 2009/387, and is a follow-on to the umbrella case PSARC 2009/399. The project also uses and extends interfaces from NFSv4 Mirror Mounts, PSARC 2007/416; most of the automatic mounting code and all of the automatic unmounting code is untouched. This work is based on replication/migration primitives defined in NFSv4 (RFC 3530)[1] with behaviour defined by later work [2]. B. Scope The NFSv4 working group in the IETF is working on Federated FS, which is a unified, centrally managed back-end to support a set of servers presenting a uniform namespace. This project is not delivering support for Federated FS since that specification is still a work-in-progress. However, our work will permit drop-in support of FedFS in the future. This project is not delivering support for replication and migration as described by the NFSv4 specification. Solaris currently has limited support for replication and client-side failover via mount_nfs(1M) and the automounter via PSARC 1995/143. This work is expected to be a basis for future migration support. C. Behaviour C.1 Client Behaviour The client discovers referral objects as it examines the NFSv4 server's filesystems, and the client associates a distinct set of vnode ops with these objects. Most client filesystem operations will trigger referral mounts, but VOP_LOOKUP() and most VOP_GETATTR() calls will not, to match existing automount and mirror mount behaviour. Prior to a mount, the NFSv4 client will display referral objects as directories with artificial metadata, like autofs trigger nodes before mounting. As with mirror mounts, find(1)'s use of _AT_TRIGGER (PSARC 2007/563) will force a mount prior to collecting attributes. Mounting will be done without checking the privilege of the calling process. Automatic umounting will be done in the same way as for mirror mounts. Mounts will time out like mounts done by the automounter, and a manual unmount of the enclosing filesystem will unmount referral mounts and mirror mounts as well unless they are being kept busy by processes' open files. The NFSv4 client will advertise support for referrals via the protocol's SETCLIENTID operation; see section C.2 for more. The client will perform a mount of the first reachable location in the fs_locations data. The multi-valued "fs_locations" attribute describes the locations (server:/path combinations) for the same data. fs_locations can use hostnames, dotted quad numeric IPv4 address strings, or IPv6 address strings; we will convert these according to the client's transport configuration by doing a new door upcall to the existing nfsmapid binary. A new string, "referral", will be visible in "nfsstat -m" output for an automatic mount done this way. Other observability will include a kstat counter of referral mounts done and a number of dtrace probes to report the results of name resolution and mounts. A kernel tunable will permit disabling referral mounts if it should be deemed necessary, but it will not be documented. C.2 Server Behaviour When NFSv3 and NFSv4 server processes operations on behalf of the client, it may encounter reparse points (as described in PSARC 2009/387). When that occurs, the server will examine the reparse point data and look for a service type starting with 'nfs', indicating NFS service data. If found, the NFSv4 server will normally return NFS4ERR_MOVED. The NFSv4 client will then normally request the fs_locations attribute. In response to this, the NFSv4 server will upcall with the NFS service data to the reparse daemon. In general, with reparse points, the service data can be a key to find the desired location information, perhaps by consulting a distributed or networked database. For this first release, the service data will simply be the location information in the form of a "host:/path [host:/path ...]" string. This has the property that the referral will work when the filesystem containing it is replicated or moved to another system. The reparse point plugin for our "nfs-basic" service will be provided to convert the location information fs_locations data. The server will return this fs_locations to referral-aware NFSv4 clients. One of the goals of this project is to allow non-referral- aware NFSv4 and NFSv3 clients to participate in the namespace. This is accomplished by translating the first referral location into a '/net'-based symbolic link. This always happens for NFSv3. This will permit the majority of NFSv3 clients to see and use the namespace, since Solaris, Linux and MacOS X all support compatible /net operation in their automounters. The NFSv4 server examines the data from the client's SETCLIENTID operation to determine if the client advertises referral support. For Solaris clients that do not support referrals, the Solaris server will return a symlink which the Solaris client will be able to correctly interpret. To manage referrals, a simple 'nfsref' command will be provided. It will live in /usr/sbin/nfsref and will support three commands: Usage: nfsref [-t type] add path location [location ...] nfsref [-t type] remove path nfsref [-t type] lookup path In all cases 'path' is the reparse point symlink involved. 'add' will add NFS service data to the reparse point, creating the symlink if necessary. Other service types' records will be left intact, but an existing 'nfs-basic' entry will be replaced. 'remove' will remove NFS service data from the reparse point, deleting the symlink if no other service type entries exist. The 'nfsref add' and 'nfsref remove' commands will require the filesystem permissions to create or remove a symlink at the specified path, and 'nfsref lookup' will require the filesystem permissions to lookup and read the symlink. Observability will include a kstat counter of the number of referrals issued and a number of dtrace probes to report the results of upcalls. D. Interface Table Imported interfaces |Specified | |in what | Interface Name |Document? |Comments ============================================================ XAT_REPARSE |PSARC 2009/387 |Reparse extensible |Private |attribute | | reparse_kderef |PSARC 2009/387 |Reparse kernel reparse_init | |routines reparse_parse | | reparse_free | | | | reparse_init |PSARC 2009/387 |Reparse library reparse_parse | |routines reparse_add | | reparse_remove | | reparse_unparse | | reparse_free | | reparse_create | | reparse_delete | | reparse_deref | | | | reparse_plugin_ops_t |PSARC 2009/387 |Reparse plugin | |ops libuuid |PSARC 2002/094 |uuid_generate_random Exported interfaces |Proposed |Specified | |Stability |in what | Interface Name |Classification |Document? | Comments ============================================================================== reparse point syntax |Committed Private| |service type nfs-basic for NFS referrals | | | | | | /usr/lib/reparse/ |Project Private | |reparse point plugin libnfs_basic.so.1 | | | | | | /usr/sbin/nfsref |Committed | |NFS referrals command | | | nfs4_no_referrals |Project Private | |tunable to disable | | |referrals on client | | | nfsstat -m format |Unstable | |new "referrals" string | | | kstat counters |Project Private | |referrals & upcalls for "nfsstat -c/-s" | | |for observability | | | Dtrace probes |Project Private | |client and server | | |observability | | | SETCLIENTID format |Committed Private| |Add "+referrals" E. References [1] Network File System (NFS) version 4 Protocol http://www.ietf.org/rfc/rfc3530.txt [2] Implementation Guide for Referrals in NFSv4 http://tools.ietf.org/html/draft-ietf-nfsv4-referrals-00.txt 6. Resources and Schedule 6.4. Steering Committee requested information 6.4.1. Consolidation C-team Name: ON 6.5. ARC review type: FastTrack 6.6. ARC Exposure: open From Calum.Mackay@Sun.COM Fri Sep 18 16:04:37 2009 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n8IN4aeZ025943 for ; Fri, 18 Sep 2009 16:04:37 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id n8IN4YmT021116; Sat, 19 Sep 2009 07:04:35 +0800 (SGT) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KQ600103W3LH300@nwk-avmta-1.sfbay.Sun.COM>; Fri, 18 Sep 2009 16:04:33 -0700 (PDT) Received: from gmp-eb-inf-2.sun.com ([192.18.6.24]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KQ600AOGW3K8M70@nwk-avmta-1.sfbay.Sun.COM>; Fri, 18 Sep 2009 16:04:33 -0700 (PDT) Received: from fe-emea-09.sun.com (gmp-eb-lb-1-fe1.eu.sun.com [192.18.6.7] (may be forged)) by gmp-eb-inf-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id n8IN4WjF028931; Fri, 18 Sep 2009 23:04:32 +0000 (GMT) Received: from conversion-daemon.fe-emea-09.sun.com by fe-emea-09.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) id <0KQ600M00VWWDQ00@fe-emea-09.sun.com>; Sat, 19 Sep 2009 00:04:19 +0100 (BST) Received: from [192.168.254.1] ([unknown] [83.217.170.67]) by fe-emea-09.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) with ESMTPSA id <0KQ600LEIW352ZD0@fe-emea-09.sun.com>; Sat, 19 Sep 2009 00:04:19 +0100 (BST) Date: Sat, 19 Sep 2009 00:04:16 +0100 From: Calum Mackay Subject: Re: NFS Referrals [PSARC/2009/502 FastTrack timeout 09/25/2009] In-reply-to: <200909182251.n8IMpamV025443@sac.sfbay.sun.com> Sender: Calum.Mackay@Sun.COM To: Rich.Brown@Sun.COM Cc: PSARC-ext@Sun.COM, nfs-referrals@Sun.COM Message-id: <4AB411F0.9090303@sun.com> Organization: Sun Microsystems MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200909182251.n8IMpamV025443@sac.sfbay.sun.com> User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.9.1.1) Gecko/20090715 Thunderbird/3.0b3 Status: RO Content-Length: 572 Rich, > To manage referrals, a simple 'nfsref' command will be provided. > It will live in /usr/sbin/nfsref and will support three commands: > Usage: > nfsref [-t type] add path location [location ...] > nfsref [-t type] remove path > nfsref [-t type] lookup path Have the team considered creating a single unified command to manage all NFS-related admin on the server (and client, indeed), rather than introducing individual commands whenever new functionality is needed? That's presuming that the SMF service itself can't be used to house the data? cheers, c. From lists@mcintyreweb.com Fri Sep 18 19:41:58 2009 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n8J2fw7e028029 for ; Fri, 18 Sep 2009 19:41:58 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n8J2fulI026338; Sat, 19 Sep 2009 03:41:56 +0100 (BST) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KQ70090165VB700@nwk-avmta-1.sfbay.Sun.COM>; Fri, 18 Sep 2009 19:41:55 -0700 (PDT) Received: from sca-ea-mail-3.sun.com ([192.18.43.21]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KQ7003RC65VB0A0@nwk-avmta-1.sfbay.Sun.COM>; Fri, 18 Sep 2009 19:41:55 -0700 (PDT) Received: from relay42i.sun.com ([192.5.209.72]) by sca-ea-mail-3.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n8J2fsGl029162; Sat, 19 Sep 2009 02:41:55 +0000 (GMT) Received: from mms48es.mms.us.syntegra.com ([160.41.221.230] [160.41.221.230]) by relay42i.sun.com with ESMTP id BT-MMP-1399101; Sat, 19 Sep 2009 02:41:54 +0000 (Z) Received: from relay42i.sun.com (relay42i.sun.com [192.5.209.72]) by mms48es.mms.us.syntegra.com with ESMTP id BT-MMP-15074318; Sat, 19 Sep 2009 02:41:54 +0000 (Z) Received: from remote.mcintyreweb.com ([67.23.1.228] [67.23.1.228]) by relay4i.sun.com with ESMTP id BT-MMP-30053990; Sat, 19 Sep 2009 02:41:54 +0000 (Z) Received: from twins.i.mcintyreweb.com (unknown [64.166.3.74]) by remote.mcintyreweb.com (Postfix) with ESMTPS id C533610C232; Fri, 18 Sep 2009 19:42:57 -0700 (PDT) Date: Fri, 18 Sep 2009 19:41:51 -0700 From: Hugh McIntyre Subject: Re: NFS Referrals [PSARC/2009/502 FastTrack timeout 09/25/2009] In-reply-to: <200909182251.n8IMpamV025443@sac.sfbay.sun.com> To: Rich.Brown@sun.com Cc: PSARC-ext@sun.com, nfs-referrals@sun.com Message-id: <4AB444EF.2020700@mcintyreweb.com> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 X-Brightmail-Tracker: AAAAAA== X-Antispam: No, score=0.0/5.0, scanned in 0.167sec at (localhost [127.0.0.1]) by smf-spamd v1.3.1 - http://smfs.sf.net/ References: <200909182251.n8IMpamV025443@sac.sfbay.sun.com> User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812) Status: RO Content-Length: 216 Rich.Brown@sun.com wrote: > ... the service data will simply be the location > information in the form of a "host:/path [host:/path ...]" > string. Dumb question: what happens if the path contains a space? Hugh. From robert.thurlow@sun.com Sat Sep 19 06:20:34 2009 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n8JDKXkJ006007 for ; Sat, 19 Sep 2009 06:20:34 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id n8JDKPcJ025018; Sat, 19 Sep 2009 21:20:29 +0800 (SGT) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KQ700E0FZQ4I800@nwk-avmta-2.sfbay.sun.com>; Sat, 19 Sep 2009 06:20:28 -0700 (PDT) Received: from jurassic-x4600.sfbay.sun.com ([129.146.17.63]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KQ700AN1ZQ4OH10@nwk-avmta-2.sfbay.sun.com>; Sat, 19 Sep 2009 06:20:28 -0700 (PDT) Received: from [10.7.251.51] (punchin-client-10-7-251-51.SFBay.Sun.COM [10.7.251.51]) by jurassic-x4600.sfbay.sun.com (8.14.3+Sun/8.14.3) with ESMTP id n8JDKMgw807186; Sat, 19 Sep 2009 06:20:27 -0700 (PDT) Date: Sat, 19 Sep 2009 07:20:22 -0600 From: Robert Thurlow Subject: Re: NFS Referrals [PSARC/2009/502 FastTrack timeout 09/25/2009] In-reply-to: <4AB411F0.9090303@sun.com> To: Calum Mackay Cc: Rich.Brown@sun.com, PSARC-ext@sun.com, nfs-referrals@sun.com Message-id: <4AB4DA96.5090000@sun.com> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200909182251.n8IMpamV025443@sac.sfbay.sun.com> <4AB411F0.9090303@sun.com> User-Agent: Thunderbird 2.0.0.16 (X11/20080811) Status: RO Content-Length: 980 Calum Mackay wrote: > Have the team considered creating a single unified command to manage all > NFS-related admin on the server (and client, indeed), rather than > introducing individual commands whenever new functionality is needed? We haven't revisited this in awhile. The existence of share manager puts a lot of existing facts in the way. > That's presuming that the SMF service itself can't be used to house the > data? An earlier version of this proposal had a local database which could have been converted to SMF, but the problem with that was that extra information was tied to the single server where the data happened to be housed, and was not available if the data was moved or copied. That would be the case with SMF as well. We simplified the proposal to store all of the data together, but a next step would be to move to a distributed or network database, which configuration would look a lot like the FedFS work in the NFSv4 IETF working group. Rob T From robert.thurlow@sun.com Sat Sep 19 06:26:12 2009 Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n8JDQCwc006042 for ; Sat, 19 Sep 2009 06:26:12 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n8JDQ7Zw030165; Sat, 19 Sep 2009 07:26:11 -0600 (MDT) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KQ700709ZZMK400@nwk-avmta-1.sfbay.Sun.COM>; Sat, 19 Sep 2009 06:26:10 -0700 (PDT) Received: from jurassic-x4600.sfbay.sun.com ([129.146.17.63]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KQ70072QZZLF200@nwk-avmta-1.sfbay.Sun.COM>; Sat, 19 Sep 2009 06:26:10 -0700 (PDT) Received: from [10.7.251.51] (punchin-client-10-7-251-51.SFBay.Sun.COM [10.7.251.51]) by jurassic-x4600.sfbay.sun.com (8.14.3+Sun/8.14.3) with ESMTP id n8JDQ9YZ807374; Sat, 19 Sep 2009 06:26:09 -0700 (PDT) Date: Sat, 19 Sep 2009 07:26:08 -0600 From: Robert Thurlow Subject: Re: NFS Referrals [PSARC/2009/502 FastTrack timeout 09/25/2009] In-reply-to: <4AB4DA96.5090000@sun.com> Cc: Rich.Brown@sun.com, PSARC-ext@sun.com, nfs-referrals@sun.com Message-id: <4AB4DBF0.7050001@sun.com> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200909182251.n8IMpamV025443@sac.sfbay.sun.com> <4AB411F0.9090303@sun.com> <4AB4DA96.5090000@sun.com> User-Agent: Thunderbird 2.0.0.16 (X11/20080811) Status: RO Content-Length: 471 Hugh McIntyre wrote: >Rich.Brown@sun.com wrote: >> ... the service data will simply be the location >> information in the form of a "host:/path [host:/path ...]" >> string. > Dumb question: what happens if the path contains a space? The user will have to escape the path to get the shell to see it as a single argument, and we will store it with spaces escaped with a backslash (and we'll escape backslashes from the user as well). Rob T From Calum.Mackay@sun.com Mon Sep 21 02:27:43 2009 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n8L9RgR9005804 for ; Mon, 21 Sep 2009 02:27:43 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id n8L9Rd3f025184; Mon, 21 Sep 2009 17:27:41 +0800 (SGT) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KQB00L0FEA4E400@nwk-avmta-1.sfbay.Sun.COM>; Mon, 21 Sep 2009 02:27:40 -0700 (PDT) Received: from gmp-eb-inf-2.sun.com ([192.18.6.24]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KQB00HYFEA3ZEB0@nwk-avmta-1.sfbay.Sun.COM>; Mon, 21 Sep 2009 02:27:40 -0700 (PDT) Received: from fe-emea-10.sun.com (gmp-eb-lb-1-fe1.eu.sun.com [192.18.6.7] (may be forged)) by gmp-eb-inf-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id n8L9RcY3012457; Mon, 21 Sep 2009 09:27:39 +0000 (GMT) Received: from conversion-daemon.fe-emea-10.sun.com by fe-emea-10.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) id <0KQB00B00DA2WT00@fe-emea-10.sun.com>; Mon, 21 Sep 2009 10:27:24 +0100 (BST) Received: from [192.168.254.1] ([unknown] [83.217.170.67]) by fe-emea-10.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) with ESMTPSA id <0KQB00EM7E95RZ50@fe-emea-10.sun.com>; Mon, 21 Sep 2009 10:27:07 +0100 (BST) Date: Mon, 21 Sep 2009 10:27:05 +0100 From: Calum Mackay Subject: Re: NFS Referrals [PSARC/2009/502 FastTrack timeout 09/25/2009] In-reply-to: <4AB4DA96.5090000@sun.com> Sender: Calum.Mackay@sun.com To: Robert Thurlow Cc: Rich.Brown@sun.com, PSARC-ext@sun.com, nfs-referrals@sun.com Message-id: <4AB746E9.5030107@sun.com> Organization: Sun Microsystems MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200909182251.n8IMpamV025443@sac.sfbay.sun.com> <4AB411F0.9090303@sun.com> <4AB4DA96.5090000@sun.com> User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.9.1.1) Gecko/20090715 Thunderbird/3.0b3 Status: RO Content-Length: 794 thanks Rob, >> Have the team considered creating a single unified command to manage >> all NFS-related admin on the server (and client, indeed), rather than >> introducing individual commands whenever new functionality is needed? > > We haven't revisited this in awhile. The existence of > share manager puts a lot of existing facts in the way. Quite; I suppose the obvious follow-on question is: would this new functionality be better located as a share manager sub-command? It does seem closely related to sharing, of course... that could still be done, independently of where the back-end data is stored. > step would be to move to a distributed or network database, > which configuration would look a lot like the FedFS work > in the NFSv4 IETF working group. yup. cheers, calum. From Rich.Brown@sun.com Mon Sep 21 06:49:58 2009 Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk.SFBay.Sun.COM [129.146.11.52]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n8LDnweo009411 for ; Mon, 21 Sep 2009 06:49:58 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail3mpk.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.4) with ESMTP id n8LDnu2j005295; Mon, 21 Sep 2009 06:49:57 -0700 (PDT) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KQB0010JQF8P900@nwk-avmta-2.sfbay.sun.com>; Mon, 21 Sep 2009 06:49:56 -0700 (PDT) Received: from brmea-mail-1.sun.com ([192.18.98.31]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KQB001P5QF7DX00@nwk-avmta-2.sfbay.sun.com>; Mon, 21 Sep 2009 06:49:55 -0700 (PDT) Received: from fe-amer-09.sun.com ([192.18.109.79]) by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n8LDnt30001759; Mon, 21 Sep 2009 13:49:55 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) id <0KQB00400Q09JN00@mail-amer.sun.com>; Mon, 21 Sep 2009 07:49:55 -0600 (MDT) Received: from [129.147.9.28] ([unknown] [129.147.9.28]) by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) with ESMTPSA id <0KQB00G3YQF69650@mail-amer.sun.com>; Mon, 21 Sep 2009 07:49:55 -0600 (MDT) Date: Mon, 21 Sep 2009 08:49:54 -0500 From: Rich Brown Subject: Re: NFS Referrals [PSARC/2009/502 FastTrack timeout 09/25/2009] In-reply-to: <200909182251.n8IMpamV025443@sac.sfbay.sun.com> Sender: Rich.Brown@sun.com To: PSARC-ext@sun.com Cc: nfs-referrals@sun.com Message-id: <4AB78482.5070809@Sun.COM> MIME-version: 1.0 Content-type: multipart/mixed; boundary="Boundary_(ID_4vqvq5oyuzML9s75OyKgig)" X-PMX-Version: 5.4.1.325704 References: <200909182251.n8IMpamV025443@sac.sfbay.sun.com> User-Agent: Thunderbird 2.0.0.21 (X11/20090311) Status: RO Content-Length: 3707 This is a multi-part message in MIME format. --Boundary_(ID_4vqvq5oyuzML9s75OyKgig) Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT I forgot to include the man page for the proposed nfsref(1M) command when I submitted this case on Friday afternoon. This command, as proposed, is straightforward and is already described in the text of the fast-track. I've put a copy of the man page in the case directory for completeness and have attached a copy to this note. Once this case closes, I'll have the team up the the man page and add it to the case directory. My apologies for this oversight, Rich --Boundary_(ID_4vqvq5oyuzML9s75OyKgig) Content-type: text/plain; name=nfsref.1M.txt Content-transfer-encoding: 7BIT Content-disposition: inline; filename=nfsref.1M.txt System Administration Commands reparsed(1M) NAME nfsref - NFS referral utility SYNOPSIS nfsref [-t svc_type] addR path location [location ...] nfsref [-t svc_type] removeR path nfsref [-t svc_type] lookupR path DESCRIPTION The nfsref command manages NFS Version 4 referrals, which are server-side pointers used to redirect clients to actual locations of filesystems. Referrals are based on reparse points (see reparsed(1M) and libreparse(1M)). The path arguments in all forms of the synopsis refer to the path to the reparse point symbolic link. This command currently implements one "service type" - "nfs-basic". The first form, nfsref add, will create a referral pointing to the given locations. If a reparse point does not exist, one will be created, and if it does exist, NFS service data will be added or will replace existing NFS service data. The second form, nfsref delete, will remove an NFS referral. It will remove NFS service data from the given reparse point, and will remove the reparse point if there are no other types of service data present. The first form, nfsref lookup, will display to what loca- tions the NFS referral points. EXAMPLES Example 1 Adding an NFS referral The following command creates an NFS referral at the server path /pool/home/bob, pointing to the resource homeserver:/homepool/bob. # nfsref add /pool/home/bob homeserver:/homepool/bob Created reparse point /pool/home/bob # nfsref lookup /pool/home/bob /pool/home/bob points to: homeserver:/homepool/bob SunOS 5.11 Last change: 18 Sep 2009 1 System Administration Commands reparsed(1M) Example 1 Removing an NFS referral The following command removes an NFS referral at the server path /pool/home/bob. # nfsref remove /pool/home/bob homeserver:/homepool/bob Removed svc_type 'nfs-basic' from /pool/home/bob EXIT STATUS 0 Successful completion. >0 An error occurred. FILES /usr/lib/reparsed/*.so.1 Per-service plugins for reparsed. ATTRIBUTES See attributes(5) for descriptions of the following attri- butes: ____________________________________________________________ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | |_____________________________|_____________________________| | Availability | SUNWnfssu | |_____________________________|_____________________________| | Interface Stability | Consolidation Private | |_____________________________|_____________________________| SEE ALSO libreparse(3reparse), attributes(5) SunOS 5.11 Last change: 18 Sep 2009 2 --Boundary_(ID_4vqvq5oyuzML9s75OyKgig)-- From Joerg.Barfurth@sun.com Tue Sep 22 01:11:10 2009 Received: from sunmail2sca.sfbay.sun.com (sunmail2sca.SFBay.Sun.COM [129.145.155.234]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n8M8BA4u019056 for ; Tue, 22 Sep 2009 01:11:10 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail2sca.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.4) with ESMTP id n8M8ArAV002606; Tue, 22 Sep 2009 01:11:10 -0700 (PDT) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KQD00M0H5EK7E00@brm-avmta-1.central.sun.com>; Tue, 22 Sep 2009 02:11:08 -0600 (MDT) Received: from gmp-eb-inf-2.sun.com ([192.18.6.24]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KQD00EDK5EH5K40@brm-avmta-1.central.sun.com>; Tue, 22 Sep 2009 02:11:06 -0600 (MDT) Received: from fe-emea-10.sun.com (gmp-eb-lb-1-fe1.eu.sun.com [192.18.6.7] (may be forged)) by gmp-eb-inf-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id n8M8B4jc026095; Tue, 22 Sep 2009 08:11:05 +0000 (GMT) Received: from conversion-daemon.fe-emea-10.sun.com by fe-emea-10.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) id <0KQD00G003JPN300@fe-emea-10.sun.com>; Tue, 22 Sep 2009 09:10:54 +0100 (BST) Received: from [10.16.66.63] ([unknown] [10.16.66.63]) by fe-emea-10.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) with ESMTPSA id <0KQD0033Y5DKROH0@fe-emea-10.sun.com>; Tue, 22 Sep 2009 09:10:33 +0100 (BST) Date: Tue, 22 Sep 2009 10:10:32 +0200 From: Joerg Barfurth Subject: Re: NFS Referrals [PSARC/2009/502 FastTrack timeout 09/25/2009] In-reply-to: <4AB78482.5070809@Sun.COM> Sender: Joerg.Barfurth@sun.com To: Rich Brown Cc: PSARC-ext@sun.com, nfs-referrals@sun.com Message-id: <4AB88678.4080003@sun.com> Organization: Sun Microsystem - Desktop MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 8BIT X-PMX-Version: 5.4.1.325704 References: <200909182251.n8IMpamV025443@sac.sfbay.sun.com> <4AB78482.5070809@Sun.COM> User-Agent: Thunderbird 2.0.0.17 (X11/20081014) Status: RO Content-Length: 1095 Rich Brown schrieb: > I forgot to include the man page for the proposed nfsref(1M) command > when I submitted this case on Friday afternoon. > > This command, as proposed, is straightforward and is already described > in the text of the fast-track. I've put a copy of the man page in the > case directory for completeness and have attached a copy to this note. > You only give 'Committed' as overall nfsref stability. Does this extend to nfsref lookup output? Can you provide a way to (optionally) have an output format better suited to parsing/scripting than " points to: " [" " ]* (format of multi-location output my assumption)? And picking up the question of spaces: how will spaces be handled in nfsref lookup output? - Jörg -- Joerg Barfurth phone: +49 40 23646662 / x66662 Software Engineer mailto:joerg.barfurth@sun.com Desktop Technology http://reserv.ireland/twiki/bin/view/Argus/ Thin Client Software http://www.sun.com/software/sunray/ Sun Microsystems GmbH http://www.sun.com/software/javadesktopsystem/ From robert.thurlow@sun.com Tue Sep 22 08:32:07 2009 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n8MFW5tT026456 for ; Tue, 22 Sep 2009 08:32:06 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id n8MFVkfp018530; Tue, 22 Sep 2009 23:32:00 +0800 (SGT) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KQD00401PT7P900@nwk-avmta-1.sfbay.Sun.COM>; Tue, 22 Sep 2009 08:31:55 -0700 (PDT) Received: from jurassic-x4600.sfbay.sun.com ([129.146.17.59]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KQD002WUPT6GBC0@nwk-avmta-1.sfbay.Sun.COM>; Tue, 22 Sep 2009 08:31:55 -0700 (PDT) Received: from [10.7.251.51] (punchin-client-10-7-251-51.SFBay.Sun.COM [10.7.251.51]) by jurassic-x4600.sfbay.sun.com (8.14.3+Sun/8.14.3) with ESMTP id n8MFVsbB343863; Tue, 22 Sep 2009 08:31:54 -0700 (PDT) Date: Tue, 22 Sep 2009 09:31:50 -0600 From: Robert Thurlow Subject: Re: NFS Referrals [PSARC/2009/502 FastTrack timeout 09/25/2009] In-reply-to: <4AB746E9.5030107@sun.com> To: Calum Mackay Cc: Rich.Brown@sun.com, PSARC-ext@sun.com, nfs-referrals@sun.com Message-id: <4AB8EDE6.8080506@sun.com> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200909182251.n8IMpamV025443@sac.sfbay.sun.com> <4AB411F0.9090303@sun.com> <4AB4DA96.5090000@sun.com> <4AB746E9.5030107@sun.com> User-Agent: Thunderbird 2.0.0.16 (X11/20080811) Status: RO Content-Length: 1001 Calum Mackay wrote: >>> Have the team considered creating a single unified command to manage >>> all NFS-related admin on the server (and client, indeed), rather than >>> introducing individual commands whenever new functionality is needed? >> >> We haven't revisited this in awhile. The existence of >> share manager puts a lot of existing facts in the way. > > Quite; I suppose the obvious follow-on question is: would this new > functionality be better located as a share manager sub-command? It does > seem closely related to sharing, of course... that could still be done, > independently of where the back-end data is stored. I thought about this. I think the syntax would be quite straightforward, but I think I'd have a hard time making the sysadmin docs on sharemgr make sense of this addition. Everything else about sharemgr is about filesystem attributes and, well, shares, and this is more about a particular pathname. So I guess it didn't seem a great fit to me in the end. Rob T From robert.thurlow@sun.com Tue Sep 22 08:41:36 2009 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n8MFfZIt026521 for ; Tue, 22 Sep 2009 08:41:35 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n8MFfOIM011416; Tue, 22 Sep 2009 16:41:33 +0100 (BST) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KQD00D0LQ979200@nwk-avmta-2.sfbay.sun.com>; Tue, 22 Sep 2009 08:41:31 -0700 (PDT) Received: from jurassic-x4600.sfbay.sun.com ([129.146.17.63]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KQD0064HQ95QR90@nwk-avmta-2.sfbay.sun.com>; Tue, 22 Sep 2009 08:41:29 -0700 (PDT) Received: from [10.7.251.51] (punchin-client-10-7-251-51.SFBay.Sun.COM [10.7.251.51]) by jurassic-x4600.sfbay.sun.com (8.14.3+Sun/8.14.3) with ESMTP id n8MFfJKj344683; Tue, 22 Sep 2009 08:41:20 -0700 (PDT) Date: Tue, 22 Sep 2009 09:41:19 -0600 From: Robert Thurlow Subject: Re: NFS Referrals [PSARC/2009/502 FastTrack timeout 09/25/2009] In-reply-to: <4AB88678.4080003@sun.com> To: Joerg Barfurth Cc: Rich Brown , PSARC-ext@sun.com, nfs-referrals@sun.com Message-id: <4AB8F01F.4060606@sun.com> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200909182251.n8IMpamV025443@sac.sfbay.sun.com> <4AB78482.5070809@Sun.COM> <4AB88678.4080003@sun.com> User-Agent: Thunderbird 2.0.0.16 (X11/20080811) Status: RO Content-Length: 1311 Joerg Barfurth wrote: > Rich Brown schrieb: >> I forgot to include the man page for the proposed nfsref(1M) command >> when I submitted this case on Friday afternoon. >> >> This command, as proposed, is straightforward and is already described >> in the text of the fast-track. I've put a copy of the man page in the >> case directory for completeness and have attached a copy to this note. >> > > You only give 'Committed' as overall nfsref stability. Does this extend > to nfsref lookup output? > > Can you provide a way to (optionally) have an output format better > suited to parsing/scripting than > " points to: " [" " ]* > (format of multi-location output my assumption)? I should have specified the output as Unstable; I don't think scripting based on the command is a good idea, and it may change as we get more experience with this stuff. Since the symlink format is Committed, you could script on "ls -l" output with some parsing effort, or your application could make use of libreparse.so. > And picking up the question of spaces: how will spaces be handled in > nfsref lookup output? Embedded spaces are currently just printed: # nfsref add /bbb h1:/p1 "h2:/p2 p2a" Added to reparse point /bbb # nfsref lookup /bbb /bbb points to: h1:/p1 h2:/p2 p2a Rob T From Calum.Mackay@sun.com Tue Sep 22 08:46:23 2009 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n8MFkMPh026602 for ; Tue, 22 Sep 2009 08:46:23 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id n8MFkIi5025464; Tue, 22 Sep 2009 23:46:21 +0800 (SGT) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KQD00L05QH8FX00@brm-avmta-1.central.sun.com>; Tue, 22 Sep 2009 09:46:20 -0600 (MDT) Received: from gmp-eb-inf-2.sun.com ([192.18.6.24]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KQD00CCDQH6HY90@brm-avmta-1.central.sun.com>; Tue, 22 Sep 2009 09:46:19 -0600 (MDT) Received: from fe-emea-09.sun.com (gmp-eb-lb-1-fe1.eu.sun.com [192.18.6.7] (may be forged)) by gmp-eb-inf-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id n8MFkH18006961; Tue, 22 Sep 2009 15:46:18 +0000 (GMT) Received: from conversion-daemon.fe-emea-09.sun.com by fe-emea-09.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) id <0KQD00900Q4B2A00@fe-emea-09.sun.com>; Tue, 22 Sep 2009 16:46:10 +0100 (BST) Received: from [192.168.12.29] ([unknown] [212.44.17.104]) by fe-emea-09.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) with ESMTPSA id <0KQD00DW9QGJEJF0@fe-emea-09.sun.com>; Tue, 22 Sep 2009 16:46:01 +0100 (BST) Date: Tue, 22 Sep 2009 16:45:53 +0100 From: Calum Mackay Subject: Re: NFS Referrals [PSARC/2009/502 FastTrack timeout 09/25/2009] In-reply-to: <4AB8EDE6.8080506@sun.com> Sender: Calum.Mackay@sun.com To: Robert Thurlow Cc: Rich.Brown@sun.com, PSARC-ext@sun.com, nfs-referrals@sun.com Message-id: <4AB8F131.6080907@sun.com> Organization: Sun Microsystems MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200909182251.n8IMpamV025443@sac.sfbay.sun.com> <4AB411F0.9090303@sun.com> <4AB4DA96.5090000@sun.com> <4AB746E9.5030107@sun.com> <4AB8EDE6.8080506@sun.com> User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.9.1.1) Gecko/20090715 Thunderbird/3.0b3 Status: RO Content-Length: 730 On 22/09/09 16:31, Robert Thurlow wrote: >> Quite; I suppose the obvious follow-on question is: would this new >> functionality be better located as a share manager sub-command? It >> does seem closely related to sharing, of course... that could still be >> done, independently of where the back-end data is stored. > > I thought about this. I think the syntax would be quite > straightforward, but I think I'd have a hard time making > the sysadmin docs on sharemgr make sense of this addition. > Everything else about sharemgr is about filesystem > attributes and, well, shares, and this is more about a > particular pathname. So I guess it didn't seem a great > fit to me in the end. OK, Rob, thanks for that. cheers, calum. From Joerg.Barfurth@sun.com Wed Sep 23 00:54:47 2009 Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk.SFBay.Sun.COM [129.146.11.52]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n8N7slSP015209 for ; Wed, 23 Sep 2009 00:54:47 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail3mpk.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.4) with ESMTP id n8N7sjxC007328; Wed, 23 Sep 2009 00:54:46 -0700 (PDT) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KQE00K0PZBA3F00@nwk-avmta-1.sfbay.Sun.COM>; Wed, 23 Sep 2009 00:54:46 -0700 (PDT) Received: from gmp-eb-inf-2.sun.com ([192.18.6.24]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KQE00BSVZB9WP80@nwk-avmta-1.sfbay.Sun.COM>; Wed, 23 Sep 2009 00:54:46 -0700 (PDT) Received: from fe-emea-10.sun.com (gmp-eb-lb-1-fe1.eu.sun.com [192.18.6.7] (may be forged)) by gmp-eb-inf-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id n8N7si7Z021908; Wed, 23 Sep 2009 07:54:45 +0000 (GMT) Received: from conversion-daemon.fe-emea-10.sun.com by fe-emea-10.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) id <0KQE00600Y1OZT00@fe-emea-10.sun.com>; Wed, 23 Sep 2009 08:54:38 +0100 (BST) Received: from [10.16.46.61] ([unknown] [10.16.46.61]) by fe-emea-10.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) with ESMTPSA id <0KQE00A1VZAUAW60@fe-emea-10.sun.com>; Wed, 23 Sep 2009 08:54:31 +0100 (BST) Date: Wed, 23 Sep 2009 09:54:30 +0200 From: Joerg Barfurth Subject: Re: NFS Referrals [PSARC/2009/502 FastTrack timeout 09/25/2009] In-reply-to: <4AB8F01F.4060606@sun.com> Sender: Joerg.Barfurth@sun.com To: Robert Thurlow Cc: Rich Brown , PSARC-ext@sun.com, nfs-referrals@sun.com Message-id: <4AB9D436.4@sun.com> Organization: Sun Microsystem - Desktop MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 8BIT X-PMX-Version: 5.4.1.325704 References: <200909182251.n8IMpamV025443@sac.sfbay.sun.com> <4AB78482.5070809@Sun.COM> <4AB88678.4080003@sun.com> <4AB8F01F.4060606@sun.com> User-Agent: Thunderbird 2.0.0.17 (X11/20081014) Status: RO Content-Length: 2166 Robert Thurlow schrieb: > Joerg Barfurth wrote: >> Rich Brown schrieb: >>> I forgot to include the man page for the proposed nfsref(1M) command >>> when I submitted this case on Friday afternoon. >>> >>> This command, as proposed, is straightforward and is already described >>> in the text of the fast-track. I've put a copy of the man page in the >>> case directory for completeness and have attached a copy to this note. >>> >> >> You only give 'Committed' as overall nfsref stability. Does this >> extend to nfsref lookup output? >> >> Can you provide a way to (optionally) have an output format better >> suited to parsing/scripting than >> " points to: " [" " ]* >> (format of multi-location output my assumption)? > > I should have specified the output as Unstable; What ARC calls 'Uncommitted' (there is no 'Unstable' any more) is still more stable than you think. From what you say below, you want output to be 'Not an Interface'. > I don't > think scripting based on the command is a good idea, and Why not. Things like wrapping a simple GUI (for example in python) around this come to mind. Doing a C app built on libreparse.so is significantly more effort. > it may change as we get more experience with this stuff. > Since the symlink format is Committed, you could script > on "ls -l" output with some parsing effort, or your > application could make use of libreparse.so. > >> And picking up the question of spaces: how will spaces be handled in >> nfsref lookup output? > > Embedded spaces are currently just printed: > > # nfsref add /bbb h1:/p1 "h2:/p2 p2a" > Added to reparse point /bbb > # nfsref lookup /bbb > /bbb points to: h1:/p1 h2:/p2 p2a > Uh. Here even human parsing reaches its limits, needing to reconstruct quotes as location boundaries in one's mind. - Jörg -- Joerg Barfurth phone: +49 40 23646662 / x66662 Software Engineer mailto:joerg.barfurth@sun.com Desktop Technology http://reserv.ireland/twiki/bin/view/Argus/ Thin Client Software http://www.sun.com/software/sunray/ Sun Microsystems GmbH http://www.sun.com/software/javadesktopsystem/ From robert.thurlow@sun.com Wed Sep 23 08:05:32 2009 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n8NF5V7k021719 for ; Wed, 23 Sep 2009 08:05:31 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n8NF5B50016131; Wed, 23 Sep 2009 16:05:29 +0100 (BST) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KQF00543J939K00@nwk-avmta-1.sfbay.Sun.COM>; Wed, 23 Sep 2009 08:05:27 -0700 (PDT) Received: from jurassic-x4600.sfbay.sun.com ([129.146.17.63]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KQF00481J90TB30@nwk-avmta-1.sfbay.Sun.COM>; Wed, 23 Sep 2009 08:05:24 -0700 (PDT) Received: from [10.7.251.51] (punchin-client-10-7-251-51.SFBay.Sun.COM [10.7.251.51]) by jurassic-x4600.sfbay.sun.com (8.14.3+Sun/8.14.3) with ESMTP id n8NF54GX539496; Wed, 23 Sep 2009 08:05:14 -0700 (PDT) Date: Wed, 23 Sep 2009 09:05:03 -0600 From: Robert Thurlow Subject: Re: NFS Referrals [PSARC/2009/502 FastTrack timeout 09/25/2009] In-reply-to: <4AB9D436.4@sun.com> To: Joerg Barfurth Cc: Rich Brown , PSARC-ext@sun.com, nfs-referrals@sun.com Message-id: <4ABA391F.9050004@sun.com> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200909182251.n8IMpamV025443@sac.sfbay.sun.com> <4AB78482.5070809@Sun.COM> <4AB88678.4080003@sun.com> <4AB8F01F.4060606@sun.com> <4AB9D436.4@sun.com> User-Agent: Thunderbird 2.0.0.16 (X11/20080811) Status: RO Content-Length: 923 Joerg Barfurth wrote: >> I should have specified the output as Unstable; > > What ARC calls 'Uncommitted' (there is no 'Unstable' any more) is still > more stable than you think. > > From what you say below, you want output to be 'Not an Interface'. That does match my intent, thanks for correcting. I do think this could change with more real-world experience. >>> And picking up the question of spaces: how will spaces be handled in >>> nfsref lookup output? >> >> Embedded spaces are currently just printed: >> >> # nfsref add /bbb h1:/p1 "h2:/p2 p2a" >> Added to reparse point /bbb >> # nfsref lookup /bbb >> /bbb points to: h1:/p1 h2:/p2 p2a >> > > Uh. Here even human parsing reaches its limits, needing to reconstruct > quotes as location boundaries in one's mind. Would this format be better? I could do this instead: # nfsref lookup /bbb /bbb points to: h1:/p1 h2:/p2 p2a Rob T From Nicolas.Williams@sun.com Wed Sep 23 08:47:20 2009 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n8NFlJMn022815 for ; Wed, 23 Sep 2009 08:47:19 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n8NFlBBk012061; Wed, 23 Sep 2009 16:47:15 +0100 (BST) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KQF00A0DL6O3J00@nwk-avmta-1.sfbay.Sun.COM>; Wed, 23 Sep 2009 08:47:12 -0700 (PDT) Received: from binky.Central.Sun.COM ([129.153.128.104]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KQF007MOL6O9S90@nwk-avmta-1.sfbay.Sun.COM>; Wed, 23 Sep 2009 08:47:12 -0700 (PDT) Received: from binky.Central.Sun.COM (localhost [127.0.0.1]) by binky.Central.Sun.COM (8.14.3+Sun/8.14.3) with ESMTP id n8NFhZPR022475; Wed, 23 Sep 2009 10:43:35 -0500 (CDT) Received: (from nw141292@localhost) by binky.Central.Sun.COM (8.14.3+Sun/8.14.3/Submit) id n8NFhZN9022474; Wed, 23 Sep 2009 10:43:35 -0500 (CDT) Date: Wed, 23 Sep 2009 10:43:35 -0500 From: Nicolas Williams Subject: Re: NFS Referrals [PSARC/2009/502 FastTrack timeout 09/25/2009] In-reply-to: <4ABA391F.9050004@sun.com> To: Robert Thurlow Cc: Joerg Barfurth , Rich Brown , PSARC-ext@sun.com, nfs-referrals@sun.com Message-id: <20090923154335.GD1033@Sun.COM> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline X-PMX-Version: 5.4.1.325704 References: <200909182251.n8IMpamV025443@sac.sfbay.sun.com> <4AB78482.5070809@Sun.COM> <4AB88678.4080003@sun.com> <4AB8F01F.4060606@sun.com> <4AB9D436.4@sun.com> <4ABA391F.9050004@sun.com> X-Authentication-warning: binky.Central.Sun.COM: nw141292 set sender to Nicolas.Williams@sun.com using -f User-Agent: Mutt/1.5.7i Status: RO Content-Length: 1724 On Wed, Sep 23, 2009 at 09:05:03AM -0600, Robert Thurlow wrote: > Joerg Barfurth wrote: > > >>I should have specified the output as Unstable; > > > >What ARC calls 'Uncommitted' (there is no 'Unstable' any more) is still > >more stable than you think. > > > > From what you say below, you want output to be 'Not an Interface'. > > That does match my intent, thanks for correcting. I do > think this could change with more real-world experience. You can always evolve Committed output by adding more options. I agree with Joerg here: stable output for this command, if parseable, would be very valuable. > >>>And picking up the question of spaces: how will spaces be handled in > >>>nfsref lookup output? > > Would this format be better? I could do this instead: > > # nfsref lookup /bbb > /bbb points to: > h1:/p1 > h2:/p2 p2a Embedded newlines are still a problem. Here's what I suggest: a) Add an option (say, -q) to do backslash quoting of whitespace and backslash. b) When (a) is used the output format should be Committed. c) Since the NFS referral does depend somewhat on NFS protocol version (referrals carry more information in v4.1 than in v4.0), I'd say: add a protocol version number option (say, -p), and default to v4.1. d) Don't forget that '/' too is allowed as a character in NFSv4 path components, even though POSIX doesn't, so '/' needs quoting. e) Use this output format: # nfsref lookup -q /bbb h1:/some\ path/with/\ \ crazy\ whitespace/and\/even\ slashes h2:/p2 # Note the lack of "/bbb points to:" -- that was always redundant. If you really want that in the output, then have an option for parseable output to select the above output format. Nico -- From Richard.Matthews@Sun.COM Wed Sep 23 08:57:22 2009 Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n8NFvMEK023246 for ; Wed, 23 Sep 2009 08:57:22 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n8NFuphT046604; Wed, 23 Sep 2009 09:57:21 -0600 (MDT) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KQF00I0BLNEHM00@nwk-avmta-2.sfbay.sun.com>; Wed, 23 Sep 2009 08:57:14 -0700 (PDT) Received: from brmea-mail-2.sun.com ([192.18.98.43]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KQF00FNWLNDHZ50@nwk-avmta-2.sfbay.sun.com>; Wed, 23 Sep 2009 08:57:14 -0700 (PDT) Received: from fe-amer-09.sun.com ([192.18.109.79]) by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n8NFvDTn023881; Wed, 23 Sep 2009 15:57:13 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) id <0KQF00B00IXT8X00@mail-amer.sun.com>; Wed, 23 Sep 2009 09:57:13 -0600 (MDT) Received: from [129.152.9.11] ([unknown] [129.152.9.11]) by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) with ESMTPSA id <0KQF006DALMWQA40@mail-amer.sun.com>; Wed, 23 Sep 2009 09:57:04 -0600 (MDT) Date: Wed, 23 Sep 2009 10:56:55 -0500 From: Rick Matthews Subject: Re: NFS Referrals [PSARC/2009/502 FastTrack timeout 09/25/2009] In-reply-to: <200909182251.n8IMpamV025443@sac.sfbay.sun.com> Sender: Richard.Matthews@Sun.COM To: Rich.Brown@Sun.COM Cc: PSARC-ext@Sun.COM, nfs-referrals@Sun.COM Reply-to: Richard.Matthews@Sun.COM Message-id: <4ABA4547.1030407@Sun.COM> MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200909182251.n8IMpamV025443@sac.sfbay.sun.com> User-Agent: Thunderbird 2.0.0.21 (X11/20090311) Status: RO Content-Length: 658 Nit: The submitted man page had "addR", "removeR" and "lookupR". I'm assuming the "R" is a typo. Should there be a reference to the privilege required for nfsref in the man page? +1 -- --------------------------------------------------------------------- Rick Matthews email: Rick.Matthews@sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USA main: +1(651) 554-1500 --------------------------------------------------------------------- From Rich.Brown@Sun.COM Wed Sep 23 09:00:38 2009 Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk.SFBay.Sun.COM [129.146.11.52]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n8NG0cMs023429 for ; Wed, 23 Sep 2009 09:00:38 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail3mpk.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.4) with ESMTP id n8NG0a37024958; Wed, 23 Sep 2009 09:00:38 -0700 (PDT) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KQF00A11LT0WP00@brm-avmta-1.central.sun.com>; Wed, 23 Sep 2009 10:00:36 -0600 (MDT) Received: from brmea-mail-4.sun.com ([192.18.98.36]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KQF004WHLSYSA40@brm-avmta-1.central.sun.com>; Wed, 23 Sep 2009 10:00:34 -0600 (MDT) Received: from fe-amer-09.sun.com ([192.18.109.79]) by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n8NG0YHi006885; Wed, 23 Sep 2009 16:00:34 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) id <0KQF00B00IXT8X00@mail-amer.sun.com>; Wed, 23 Sep 2009 10:00:34 -0600 (MDT) Received: from [129.147.9.28] ([unknown] [129.147.9.28]) by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) with ESMTPSA id <0KQF006LFLSRQA40@mail-amer.sun.com>; Wed, 23 Sep 2009 10:00:27 -0600 (MDT) Date: Wed, 23 Sep 2009 11:00:27 -0500 From: Rich Brown Subject: Re: NFS Referrals [PSARC/2009/502 FastTrack timeout 09/25/2009] In-reply-to: <4ABA4547.1030407@Sun.COM> Sender: Rich.Brown@Sun.COM To: Richard.Matthews@Sun.COM Cc: PSARC-ext@Sun.COM, nfs-referrals@Sun.COM Message-id: <4ABA461B.1070307@Sun.COM> MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200909182251.n8IMpamV025443@sac.sfbay.sun.com> <4ABA4547.1030407@Sun.COM> User-Agent: Thunderbird 2.0.0.21 (X11/20090311) Status: RO Content-Length: 446 On 09/23/09 10:56, Rick Matthews wrote: > Nit: The submitted man page had "addR", "removeR" and "lookupR". > I'm assuming the "R" is a typo. Yes, I thought I responded to this already but I realize it was from an off-list comment. This will be corrected in the final version. > > Should there be a reference to the privilege required for nfsref > in the man page? Yes, it will be added in the final version. > > +1 > Thanks, Rich From robert.thurlow@sun.com Wed Sep 23 09:08:41 2009 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n8NG8eRd000622 for ; Wed, 23 Sep 2009 09:08:40 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n8NG8X6X024902; Wed, 23 Sep 2009 17:08:37 +0100 (BST) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KQF00D0FM6B5N00@nwk-avmta-1.sfbay.Sun.COM>; Wed, 23 Sep 2009 09:08:35 -0700 (PDT) Received: from jurassic-x4600.sfbay.sun.com ([129.146.17.59]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KQF0077EM6B9SF0@nwk-avmta-1.sfbay.Sun.COM>; Wed, 23 Sep 2009 09:08:35 -0700 (PDT) Received: from [10.7.251.51] (punchin-client-10-7-251-51.SFBay.Sun.COM [10.7.251.51]) by jurassic-x4600.sfbay.sun.com (8.14.3+Sun/8.14.3) with ESMTP id n8NG8Ku3549786; Wed, 23 Sep 2009 09:08:20 -0700 (PDT) Date: Wed, 23 Sep 2009 10:08:19 -0600 From: Robert Thurlow Subject: Re: NFS Referrals [PSARC/2009/502 FastTrack timeout 09/25/2009] In-reply-to: <4ABA4547.1030407@Sun.COM> To: Richard.Matthews@sun.com Cc: Rich.Brown@sun.com, PSARC-ext@sun.com, nfs-referrals@sun.com Message-id: <4ABA47F3.2070601@sun.com> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200909182251.n8IMpamV025443@sac.sfbay.sun.com> <4ABA4547.1030407@Sun.COM> User-Agent: Thunderbird 2.0.0.16 (X11/20080811) Status: RO Content-Length: 384 Rick Matthews wrote: > Nit: The submitted man page had "addR", "removeR" and "lookupR". > I'm assuming the "R" is a typo. Hi Rick, Yes, that was my error in the nroff source; we'll fix it. > Should there be a reference to the privilege required for nfsref > in the man page? The only limitation is filesystem permissions on the symlink. Would we normally mention that? Rob T From Richard.Matthews@sun.com Wed Sep 23 09:16:05 2009 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n8NGG4ig021268 for ; Wed, 23 Sep 2009 09:16:04 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id n8NGFo0G026974; Thu, 24 Sep 2009 00:16:03 +0800 (SGT) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KQF00J0TMIPLL00@nwk-avmta-2.sfbay.sun.com>; Wed, 23 Sep 2009 09:16:01 -0700 (PDT) Received: from brmea-mail-4.sun.com ([192.18.98.36]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KQF00FRHMICHV60@nwk-avmta-2.sfbay.sun.com>; Wed, 23 Sep 2009 09:15:49 -0700 (PDT) Received: from fe-amer-09.sun.com ([192.18.109.79]) by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n8NGFmML015560; Wed, 23 Sep 2009 16:15:48 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) id <0KQF00900KESE200@mail-amer.sun.com>; Wed, 23 Sep 2009 10:15:48 -0600 (MDT) Received: from [129.152.9.11] ([unknown] [129.152.9.11]) by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) with ESMTPSA id <0KQF006HNMHZQA50@mail-amer.sun.com>; Wed, 23 Sep 2009 10:15:37 -0600 (MDT) Date: Wed, 23 Sep 2009 11:15:35 -0500 From: Rick Matthews Subject: Re: NFS Referrals [PSARC/2009/502 FastTrack timeout 09/25/2009] In-reply-to: <4ABA47F3.2070601@sun.com> Sender: Richard.Matthews@sun.com To: Robert Thurlow Cc: Rich.Brown@sun.com, PSARC-ext@sun.com, nfs-referrals@sun.com Reply-to: Richard.Matthews@sun.com Message-id: <4ABA49A7.80809@Sun.COM> MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200909182251.n8IMpamV025443@sac.sfbay.sun.com> <4ABA4547.1030407@Sun.COM> <4ABA47F3.2070601@sun.com> User-Agent: Thunderbird 2.0.0.21 (X11/20090311) Status: RO Content-Length: 994 On 09/23/09 11:08, Robert Thurlow wrote: > Rick Matthews wrote: >> Nit: The submitted man page had "addR", "removeR" and "lookupR". >> I'm assuming the "R" is a typo. > > Hi Rick, > > Yes, that was my error in the nroff source; we'll fix it. > >> Should there be a reference to the privilege required for nfsref >> in the man page? > > The only limitation is filesystem permissions on the symlink. > Would we normally mention that? I don't think so...wasn't sure if other permissions were also needed. Thanks. > > Rob T -- --------------------------------------------------------------------- Rick Matthews email: Rick.Matthews@sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USA main: +1(651) 554-1500 --------------------------------------------------------------------- From robert.thurlow@sun.com Wed Sep 23 09:26:39 2009 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n8NGQcPs004415 for ; Wed, 23 Sep 2009 09:26:39 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id n8NGQX6g003296; Thu, 24 Sep 2009 00:26:34 +0800 (SGT) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KQF00D0BN099K00@brm-avmta-1.central.sun.com>; Wed, 23 Sep 2009 10:26:33 -0600 (MDT) Received: from jurassic-x4600.sfbay.sun.com ([129.146.17.59]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KQF004DKN08S850@brm-avmta-1.central.sun.com>; Wed, 23 Sep 2009 10:26:33 -0600 (MDT) Received: from [10.7.251.51] (punchin-client-10-7-251-51.SFBay.Sun.COM [10.7.251.51]) by jurassic-x4600.sfbay.sun.com (8.14.3+Sun/8.14.3) with ESMTP id n8NGQRLc553180; Wed, 23 Sep 2009 09:26:28 -0700 (PDT) Date: Wed, 23 Sep 2009 10:26:27 -0600 From: Robert Thurlow Subject: Re: NFS Referrals [PSARC/2009/502 FastTrack timeout 09/25/2009] In-reply-to: <20090923154335.GD1033@Sun.COM> To: Nicolas Williams Cc: Joerg Barfurth , Rich Brown , PSARC-ext@sun.com, nfs-referrals@sun.com Message-id: <4ABA4C33.9060804@sun.com> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200909182251.n8IMpamV025443@sac.sfbay.sun.com> <4AB78482.5070809@Sun.COM> <4AB88678.4080003@sun.com> <4AB8F01F.4060606@sun.com> <4AB9D436.4@sun.com> <4ABA391F.9050004@sun.com> <20090923154335.GD1033@Sun.COM> User-Agent: Thunderbird 2.0.0.16 (X11/20080811) Status: RO Content-Length: 717 Nicolas Williams wrote: > You can always evolve Committed output by adding more options. I agree > with Joerg here: stable output for this command, if parseable, would be > very valuable. To be clear, the proposed committment level of the nfsref output is "Not An Interface". We could add a Committed parsable output when we know more about what we'd use it for. > c) Since the NFS referral does depend somewhat on NFS protocol version > (referrals carry more information in v4.1 than in v4.0), I'd say: add > a protocol version number option (say, -p), and default to v4.1. To be clear, this project is about v4.0 referrals only. v4.1 referrals will compel us to revisit this, when we get there. Rob T From Nicolas.Williams@sun.com Wed Sep 23 09:35:54 2009 Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk.SFBay.Sun.COM [129.146.11.52]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n8NGZs6W013657 for ; Wed, 23 Sep 2009 09:35:54 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail3mpk.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.4) with ESMTP id n8NGZqfr014008; Wed, 23 Sep 2009 09:35:52 -0700 (PDT) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KQF00G27NFRBJ00@nwk-avmta-1.sfbay.Sun.COM>; Wed, 23 Sep 2009 09:35:51 -0700 (PDT) Received: from binky.Central.Sun.COM ([129.153.128.104]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KQF00FRRNFQWP00@nwk-avmta-1.sfbay.Sun.COM>; Wed, 23 Sep 2009 09:35:50 -0700 (PDT) Received: from binky.Central.Sun.COM (localhost [127.0.0.1]) by binky.Central.Sun.COM (8.14.3+Sun/8.14.3) with ESMTP id n8NGWCoB022549; Wed, 23 Sep 2009 11:32:12 -0500 (CDT) Received: (from nw141292@localhost) by binky.Central.Sun.COM (8.14.3+Sun/8.14.3/Submit) id n8NGWCD9022548; Wed, 23 Sep 2009 11:32:12 -0500 (CDT) Date: Wed, 23 Sep 2009 11:32:12 -0500 From: Nicolas Williams Subject: Re: NFS Referrals [PSARC/2009/502 FastTrack timeout 09/25/2009] In-reply-to: <4ABA4C33.9060804@sun.com> To: Robert Thurlow Cc: Joerg Barfurth , Rich Brown , PSARC-ext@sun.com, nfs-referrals@sun.com Message-id: <20090923163212.GG1033@Sun.COM> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline X-PMX-Version: 5.4.1.325704 References: <200909182251.n8IMpamV025443@sac.sfbay.sun.com> <4AB78482.5070809@Sun.COM> <4AB88678.4080003@sun.com> <4AB8F01F.4060606@sun.com> <4AB9D436.4@sun.com> <4ABA391F.9050004@sun.com> <20090923154335.GD1033@Sun.COM> <4ABA4C33.9060804@sun.com> X-Authentication-warning: binky.Central.Sun.COM: nw141292 set sender to Nicolas.Williams@sun.com using -f User-Agent: Mutt/1.5.7i Status: RO Content-Length: 1301 On Wed, Sep 23, 2009 at 10:26:27AM -0600, Robert Thurlow wrote: > Nicolas Williams wrote: > > >You can always evolve Committed output by adding more options. I agree > >with Joerg here: stable output for this command, if parseable, would be > >very valuable. > > To be clear, the proposed committment level of the nfsref > output is "Not An Interface". We could add a Committed > parsable output when we know more about what we'd use it for. The command can clearly be used to script creation of referrals. Therefore it stands to reason that it should be scriptable for maintaining referrals data as well, which to me means being able to parse its output. I am not an ARC member, so you're free to ignore these comments, but I do think you'll make the product better if you accept my comments. > >c) Since the NFS referral does depend somewhat on NFS protocol version > > (referrals carry more information in v4.1 than in v4.0), I'd say: add > > a protocol version number option (say, -p), and default to v4.1. > > To be clear, this project is about v4.0 referrals only. v4.1 > referrals will compel us to revisit this, when we get there. Understood. But this is not a reason to have Not-An-Interface for the output, since you can always evolve the command by adding options. Nico -- From Rich.Brown@Sun.COM Wed Sep 23 11:22:01 2009 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n8NIM0Ha019511 for ; Wed, 23 Sep 2009 11:22:00 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id n8NILo91007508; Thu, 24 Sep 2009 02:21:59 +0800 (SGT) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KQF00601SCK5A00@nwk-avmta-1.sfbay.Sun.COM>; Wed, 23 Sep 2009 11:21:56 -0700 (PDT) Received: from brmea-mail-2.sun.com ([192.18.98.43]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KQF00FZYSCJWLD0@nwk-avmta-1.sfbay.Sun.COM>; Wed, 23 Sep 2009 11:21:56 -0700 (PDT) Received: from fe-amer-10.sun.com ([192.18.109.80]) by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n8NILtE4012885; Wed, 23 Sep 2009 18:21:55 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) id <0KQF00H00RW49N00@mail-amer.sun.com>; Wed, 23 Sep 2009 12:21:55 -0600 (MDT) Received: from [129.147.9.28] ([unknown] [129.147.9.28]) by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) with ESMTPSA id <0KQF003B4SC847D0@mail-amer.sun.com>; Wed, 23 Sep 2009 12:21:44 -0600 (MDT) Date: Wed, 23 Sep 2009 13:21:44 -0500 From: Rich Brown Subject: Re: NFS Referrals [PSARC/2009/502 FastTrack timeout 09/25/2009] In-reply-to: <200909182251.n8IMpamV025443@sac.sfbay.sun.com> Sender: Rich.Brown@Sun.COM To: PSARC-ext@Sun.COM Cc: nfs-referrals@Sun.COM Message-id: <4ABA6738.70705@Sun.COM> MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200909182251.n8IMpamV025443@sac.sfbay.sun.com> User-Agent: Thunderbird 2.0.0.21 (X11/20090311) Status: RO Content-Length: 144 This case was approved at today's PSARC meeting. I've put an updated man page in the case directory. Thank you for your time and help, Rich