From rsb@sac.sfbay.sun.com Tue Aug 21 15:11:56 2007 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 l7LMBtVk016756 for ; Tue, 21 Aug 2007 15:11:55 -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 l7LM96Un019945; Wed, 22 Aug 2007 06:09: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 <0JN50086E9JJZJ00@brm-avmta-1.central.sun.com>; Tue, 21 Aug 2007 16:09:19 -0600 (MDT) Received: from sfbaymail2sca.sfbay.sun.com ([129.145.155.42]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JN5007EM9JF5450@brm-avmta-1.central.sun.com>; Tue, 21 Aug 2007 16:09:15 -0600 (MDT) Received: from sac.sfbay.sun.com (new-sac.SFBay.Sun.COM [129.146.175.65]) by sfbaymail2sca.sfbay.sun.com (8.13.6+Sun/8.12.10/ENSMAIL,v2.2) with ESMTP id l7LM9Eo3019500; Tue, 21 Aug 2007 15:09:14 -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 l7LMBjcq016751; Tue, 21 Aug 2007 15:11:45 -0700 (PDT) Received: (from rsb@localhost) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8/Submit) id l7LMBjKv016747; Tue, 21 Aug 2007 17:11:45 -0500 (CDT) Date: Tue, 21 Aug 2007 17:11:45 -0500 (CDT) From: Richard Brown Subject: OPAQUE Moved to Readonly View [PSARC/2007/476 Self Review] To: PSARC-ext@sun.com Cc: basabi.bhattacharya@sun.com, cifs-vfs-team@sun.com, cynthia.eastham@sun.com Message-id: <200708212211.l7LMBjKv016747@sac.sfbay.sun.com> Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 Status: RO Content-Length: 2304 I'm sponsoring this case on behalf of Mark Shellenbaum. This case moves the OPAQUE optional file system attribute from the SUNattr_rw extended attribute file to the SUNWattr_ro extended attribute file. The OPAQUE attribute and the SUNWattr_rw/SUNWattr_ro extended attribute files were approved by PSARC 2007/315 "Extensible Attribute Interfaces". PSARC 2007/315 was approved with Minor binding. Note that the "Extensible Attribute" changes have *not yet* been integrated into Solaris Nevada. Since this case simply corrects an error and has not been integrated into any Solaris release, I'm filing this as Closed Approved Automatic. If anyone disagrees, let me know and I'll promote it to a fast track. Template Version: @(#)sac_nextcase 1.64 07/13/07 SMI This information is Copyright 2007 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: OPAQUE Moved to Readonly View 1.2. Name of Document Author/Supplier: Author: Mark Shellenbaum 1.3 Date of This Document: 21 August, 2007 4. Technical Description PSARC 2007/315 (Extensible Attribute Interfaces) was approved on 13 June, 2007, and introduced a set of optional system-level file attributes. A subset of those attributes were requested by a 3rd party system vendor that is porting ZFS. The OPAQUE attribute was one of the requested attributes. Recently, the project team responsible for modifying the archive utilities (cpio, tar, etc.) found that the tests were failing when they tried to restore the SUNWattr_rw extended attribute file which contained the OPAQUE attribute. The project team realized that since OPAQUE was approved as an unmodifiable optional file attribute (see the spec for PSARC 2007/315, section 3.3 "Third-Party Requested Attributes"), then it should be part of the read-only view represented by the SUNWattr_ro extended attribute file. Note that the changes originally approved by PSARC 2007/315 (Extensible Attribute Interfaces) exist only in the CIFS server project gate, have not yet been putback to Solaris Nevada, and have not been exposed to customers or developers outside of Sun. 6. Resources and Schedule 6.4. Steering Committee requested information 6.4.1. Consolidation C-team Name: ON 6.5. ARC review type: Automatic 6.6. ARC Exposure: open From carlsonj@phorcys.east.sun.com Wed Aug 22 03:43:56 2007 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 l7MAhtgv000952 for ; Wed, 22 Aug 2007 03:43:56 -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 l7MAfJtj007015; Wed, 22 Aug 2007 18:41:20 +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 <0JN6001078CVZV00@nwk-avmta-2.sfbay.sun.com>; Wed, 22 Aug 2007 03:41:19 -0700 (PDT) Received: from phorcys.east.sun.com ([129.148.174.143]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JN6003KT8CUXOC0@nwk-avmta-2.sfbay.sun.com>; Wed, 22 Aug 2007 03:41:19 -0700 (PDT) Received: from phorcys.east.sun.com (localhost [127.0.0.1]) by phorcys.east.sun.com (8.14.1+Sun/8.14.1) with ESMTP id l7MAfAeW015074; Wed, 22 Aug 2007 06:41:10 -0400 (EDT) Received: (from carlsonj@localhost) by phorcys.east.sun.com (8.14.1+Sun/8.14.1/Submit) id l7MAfAQp015071; Wed, 22 Aug 2007 06:41:10 -0400 (EDT) Date: Wed, 22 Aug 2007 06:41:10 -0400 From: James Carlson Subject: Re: OPAQUE Moved to Readonly View [PSARC/2007/476 Self Review] In-reply-to: <200708212211.l7LMBjKv016747@sac.sfbay.sun.com> To: Richard Brown Cc: PSARC-ext@sun.com, Basabi.Bhattacharya@sun.com, cifs-vfs-team@sun.com, Cynthia.Eastham@sun.com Message-id: <18124.4806.707777.195621@gargle.gargle.HOWL> MIME-version: 1.0 X-Mailer: VM 7.01 under Emacs 21.3.1 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 References: <200708212211.l7LMBjKv016747@sac.sfbay.sun.com> Status: RO Content-Length: 1360 Richard Brown writes: > Recently, the project team responsible for modifying the archive > utilities (cpio, tar, etc.) found that the tests were failing when > they tried to restore the SUNWattr_rw extended attribute file which > contained the OPAQUE attribute. The project team realized that since > OPAQUE was approved as an unmodifiable optional file attribute (see the > spec for PSARC 2007/315, section 3.3 "Third-Party Requested > Attributes"), then it should be part of the read-only view represented > by the SUNWattr_ro extended attribute file. Isn't the same true of the "SETTABLE" attribute? It's listed as failing with EPERM on all attempts, and in the SUNWattr_rw section, just like OPAQUE. Currently, it looks like the SUNWattr_ro items are all things that can be determined at mount time (FSID and MDEV), and thus the fact that these can't be changed is without consequence. But where does the OPAQUE flag come from? How does it ever get set in the first place, if it's a read-only attribute? Perhaps what's needed is a better way to tell backup utilities that certain attributes shouldn't be part of the archive. -- James Carlson, Solaris Networking Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 From Mark.Shellenbaum@sun.com Wed Aug 22 06:55:31 2007 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 l7MDtUC2004714 for ; Wed, 22 Aug 2007 06:55:31 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail5.uk.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id l7MDqmLv020947; Wed, 22 Aug 2007 14:52:56 +0100 (BST) 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 <0JN600L3PH854Y00@brm-avmta-1.central.sun.com>; Wed, 22 Aug 2007 07:52:53 -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 <0JN60016XH84MAE0@brm-avmta-1.central.sun.com>; Wed, 22 Aug 2007 07:52:53 -0600 (MDT) Received: from fe-amer-04.sun.com ([192.18.108.178]) by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id l7MDqqhi024243; Wed, 22 Aug 2007 13:52:52 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) id <0JN600K01H4DG600@mail-amer.sun.com> (original mail from Mark.Shellenbaum@Sun.COM); Wed, 22 Aug 2007 07:52:52 -0600 (MDT) Received: from [172.20.25.34] by mail-amer.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0JN600CP9H84GRI9@mail-amer.sun.com>; Wed, 22 Aug 2007 07:52:52 -0600 (MDT) Date: Wed, 22 Aug 2007 07:52:52 -0600 From: Mark Shellenbaum Subject: Re: OPAQUE Moved to Readonly View [PSARC/2007/476 Self Review] In-reply-to: <18124.4806.707777.195621@gargle.gargle.HOWL> Sender: Mark.Shellenbaum@sun.com To: James Carlson Cc: Richard Brown , PSARC-ext@sun.com, Basabi.Bhattacharya@sun.com, cifs-vfs-team@sun.com, Cynthia.Eastham@sun.com Message-id: <46CC3FB4.10605@Sun.COM> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 References: <200708212211.l7LMBjKv016747@sac.sfbay.sun.com> <18124.4806.707777.195621@gargle.gargle.HOWL> User-Agent: Thunderbird 2.0.0.4 (X11/20070703) Status: RO Content-Length: 1432 James Carlson wrote: > Richard Brown writes: >> Recently, the project team responsible for modifying the archive >> utilities (cpio, tar, etc.) found that the tests were failing when >> they tried to restore the SUNWattr_rw extended attribute file which >> contained the OPAQUE attribute. The project team realized that since >> OPAQUE was approved as an unmodifiable optional file attribute (see the >> spec for PSARC 2007/315, section 3.3 "Third-Party Requested >> Attributes"), then it should be part of the read-only view represented >> by the SUNWattr_ro extended attribute file. > > Isn't the same true of the "SETTABLE" attribute? It's listed as > failing with EPERM on all attempts, and in the SUNWattr_rw section, > just like OPAQUE. > The SETTABLE attribute was removed with Rescind SETTABLE Attribute [PSARC/2007/444 Self Review] > Currently, it looks like the SUNWattr_ro items are all things that can > be determined at mount time (FSID and MDEV), and thus the fact that > these can't be changed is without consequence. But where does the > OPAQUE flag come from? How does it ever get set in the first place, > if it's a read-only attribute? > OPAQUE is a BSD specific attribute, which is used as part of unionfs. > Perhaps what's needed is a better way to tell backup utilities that > certain attributes shouldn't be part of the archive. > Everything in the readwrite view should be archived. -Mark From carlsonj@phorcys.east.sun.com Wed Aug 22 07:18:49 2007 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 l7MEImdi005155 for ; Wed, 22 Aug 2007 07:18:49 -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.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id l7MEGAhm002242; Wed, 22 Aug 2007 15:16:12 +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 <0JN600F03IAZME00@nwk-avmta-2.sfbay.sun.com>; Wed, 22 Aug 2007 07:16:11 -0700 (PDT) Received: from phorcys.east.sun.com ([129.148.174.143]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JN600EFGIAYQR10@nwk-avmta-2.sfbay.sun.com>; Wed, 22 Aug 2007 07:16:10 -0700 (PDT) Received: from phorcys.east.sun.com (localhost [127.0.0.1]) by phorcys.east.sun.com (8.14.1+Sun/8.14.1) with ESMTP id l7MEG3c7000044; Wed, 22 Aug 2007 10:16:03 -0400 (EDT) Received: (from carlsonj@localhost) by phorcys.east.sun.com (8.14.1+Sun/8.14.1/Submit) id l7MEG2g2000041; Wed, 22 Aug 2007 10:16:02 -0400 (EDT) Date: Wed, 22 Aug 2007 10:16:02 -0400 From: James Carlson Subject: Re: OPAQUE Moved to Readonly View [PSARC/2007/476 Self Review] In-reply-to: <46CC3FB4.10605@Sun.COM> To: Mark Shellenbaum Cc: Richard Brown , PSARC-ext@sun.com, Basabi.Bhattacharya@sun.com, cifs-vfs-team@sun.com, Cynthia.Eastham@sun.com Message-id: <18124.17698.915639.430582@gargle.gargle.HOWL> MIME-version: 1.0 X-Mailer: VM 7.01 under Emacs 21.3.1 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 References: <200708212211.l7LMBjKv016747@sac.sfbay.sun.com> <18124.4806.707777.195621@gargle.gargle.HOWL> <46CC3FB4.10605@Sun.COM> Status: RO Content-Length: 960 Mark Shellenbaum writes: > > Isn't the same true of the "SETTABLE" attribute? It's listed as > > failing with EPERM on all attempts, and in the SUNWattr_rw section, > > just like OPAQUE. > > > > The SETTABLE attribute was removed with > > Rescind SETTABLE Attribute [PSARC/2007/444 Self Review] Oh ... duh. > > Currently, it looks like the SUNWattr_ro items are all things that can > > be determined at mount time (FSID and MDEV), and thus the fact that > > these can't be changed is without consequence. But where does the > > OPAQUE flag come from? How does it ever get set in the first place, > > if it's a read-only attribute? > > > > OPAQUE is a BSD specific attribute, which is used as part of unionfs. Got it; thanks. -- James Carlson, Solaris Networking Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677