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 <james.d.carlson at sun.com> 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
