1 .\" Copyright (c) 2003 Apple Computer, Inc. All rights reserved.
3 .\" The contents of this file constitute Original Code as defined in and
4 .\" are subject to the Apple Public Source License Version 1.1 (the
5 .\" "License"). You may not use this file except in compliance with the
6 .\" License. Please obtain a copy of the License at
7 .\" http://www.apple.com/publicsource and read it before using this file.
9 .\" This Original Code and all software distributed under the License are
10 .\" distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY KIND, EITHER
11 .\" EXPRESS OR IMPLIED, AND APPLE HEREBY DISCLAIMS ALL SUCH WARRANTIES,
12 .\" INCLUDING WITHOUT LIMITATION, ANY WARRANTIES OF MERCHANTABILITY,
13 .\" FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT. Please see the
14 .\" License for the specific language governing rights and limitations
15 .\" under the License.
24 .Nd get file system attributes
26 .Fd #include <sys/attr.h>
27 .Fd #include <unistd.h>
29 .Fn getattrlist "const char* path" "struct attrlist * attrList" "void * attrBuf" "size_t attrBufSize" "unsigned long options"
34 function returns attributes (that is, metadata) of file system objects.
37 as a seriously enhanced version of
39 The function returns attributes about the file system object specified by
41 in the buffer specified by
47 parameter determines what attributes are returned.
50 parameter lets you control specific aspects of the function's behaviour.
55 function is only supported by certain volume format implementations.
56 For maximum compatibility, client programs should use high-level APIs
57 (such as the Carbon File Manager) to access file system attributes.
58 These high-level APIs include logic to emulate file system attributes
59 on volumes that don't support
63 Not all volumes support all attributes.
65 .Dv ATTR_VOL_ATTRIBUTES
66 for a discussion of how to determine whether a particular volume supports a
69 Furthermore, you should only request the attributes that you need.
70 Some attributes are expensive to calculate on some volume formats.
72 .Dv ATTR_DIR_ENTRYCOUNT
73 is usually expensive to calculate on non-HFS [Plus] volumes.
74 If you don't need a particular attribute, you should not ask for it.
81 parameter must reference a valid file system object.
82 Read, write or execute permission of the object itself is not required, but
83 all directories listed in the path name leading to the object must be
87 .\" attrList parameter
91 parameter is a pointer to an
93 structure, as defined by
96 It determines what attributes are returned by the function.
97 You are responsible for filling out all fields of this structure before calling the function.
99 typedef u_int32_t attrgroup_t;
102 u_short bitmapcount; /* number of attr. bit sets in list */
103 u_int16_t reserved; /* (to maintain 4-byte alignment) */
104 attrgroup_t commonattr; /* common attribute group */
105 attrgroup_t volattr; /* volume attribute group */
106 attrgroup_t dirattr; /* directory attribute group */
107 attrgroup_t fileattr; /* file attribute group */
108 attrgroup_t forkattr; /* fork attribute group */
110 #define ATTR_BIT_MAP_COUNT 5
114 .\" attrlist elements
118 structure are defined as follows.
119 .Bl -tag -width XXXbitmapcount
122 Number of attribute bit sets in the structure.
123 In current systems you must set this to
124 .Dv ATTR_BIT_MAP_COUNT .
128 You must set this to 0.
131 A bit set that specifies the common attributes that you require.
132 Common attributes relate to all types of file system objects.
133 See below for a description of these attributes.
136 A bit set that specifies the volume attributes that you require.
137 Volume attributes relate to volumes (that is, mounted file systems).
138 See below for a description of these attributes.
139 If you request volume attributes,
141 must reference the root of a volume.
142 In addition, you can't request volume attributes if you also request
143 file or directory attributes.
146 A bit set that specifies the directory attributes that you require.
147 See below for a description of these attributes.
150 A bit set that specifies the file attributes that you require.
151 See below for a description of these attributes.
154 A bit set that specifies the fork attributes that you require.
155 Fork attributes relate to the actual data in the file,
156 which can be held in multiple named contiguous ranges, or forks.
157 See below for a description of these attributes.
162 Unless otherwise noted in the lists below, attributes are read-only.
163 Attributes labelled as read/write can be set using
167 .\" attrBuf and attrBufSize parameters
173 parameters specify a buffer into which the function places attribute values.
174 The format of this buffer is sufficiently complex that its description
175 requires a separate section (see below).
176 The initial contents of this buffer are ignored.
183 parameter is a bit set that controls the behaviour of
185 The following option bits are defined.
187 .Bl -tag -width XXXbitmapcount
192 will not follow a symlink if it occurs as
193 the last component of
200 The data returned in the buffer described by
204 is formatted as follows.
210 The first element of the buffer is a
212 that contains the overall length, in bytes, of the attributes returned.
213 This size includes the length field itself.
216 Following the length field is a list of attributes.
217 Each attribute is represented by a field of its type,
218 where the type is given as part of the attribute description (below).
221 The attributes are placed into the attribute buffer in the order
222 that they are described below.
227 If the attribute is of variable length, it is represented
230 structure, as defined by
235 typedef struct attrreference {
236 long attr_dataoffset;
242 This structure contains a 'pointer' to the variable length attribute data.
245 field is the length of the attribute data (in bytes).
248 field is the offset in bytes from the
251 to the attribute data.
252 This offset will always be a multiple of sizeof(unsigned long) bytes,
253 so you can safely access common data types without fear of alignment
259 function will silently truncate attribute data if
262 The length field at the front of the attribute list always represents
263 the length of the data actually copied into the attribute buffer.
264 If the data is truncated, there is no easy way to determine the
265 buffer size that's required to get all of the requested attributes.
266 You should always pass an
268 that is large enough to accommodate the known size of the attributes
269 in the attribute list (including the leading length field).
272 Because the returned attributes are simply truncated if the buffer is
273 too small, it's possible for a variable length attribute to reference
274 data beyond the end of the attribute buffer. That is, it's possible
275 for the attribute data to start beyond the end of the attribute buffer
279 .Vt attrreference_t ,
288 ) ) or, indeed, for the attribute data to extend beyond the end of the attribute buffer (that is,
300 If this happens you must increase the size of the buffer and call
302 to get an accurate copy of the attribute.
304 .Sh COMMON ATTRIBUTES
306 Common attributes relate to all types of file system objects.
307 The following common attributes are defined.
309 .Bl -tag -width ATTR_VOL_ALLOCATIONCLUMP
314 structure containing the name of the file system object as
315 UTF-8 encoded, null terminated C string.
316 The attribute data length will not be greater than
324 containing the device number of the device on which this
325 file system object's volume is mounted.
330 structure returned by
336 structure containing the file system identifier for the volume on which
337 the file system object resides.
342 structure returned by
346 This value is not related to the file system ID from traditional Mac OS (for example,
351 structure returned by Carbon's FSGetVolumeInfo() function).
352 On current versions of Mac OS X that value is synthesised by the Carbon File Manager.
357 that identifies the type of file system object.
358 The values are taken from
366 that identifies the type of file system containing the object.
367 The values are taken from
375 structure that uniquely identifies the file system object
377 The fid_generation field of this structure will be zero for all non-root callers
378 (effective UID not 0).
379 This identifier need not be persistent across an unmount/mount sequence.
382 Some volume formats use well known values for the
384 field for the root directory (2) and the parent of root directory (1).
385 This is not a required behaviour of this attribute.
387 .It ATTR_CMN_OBJPERMANENTID
390 structure that uniquely identifies the file system object
392 The fid_generation field of this structure will be zero for all non-root callers
393 (effective UID not 0).
394 This identifier should be persistent across an unmount/mount sequence.
396 Some file systems (for example, original HFS) may need to modify the on-disk
397 structure to return a persistent identifier.
398 If such a file system is mounted read-only, an attempt to get this attribute
399 will fail with the error
402 .It ATTR_CMN_PAROBJID
405 structure that identifies the parent directory of the file system object.
406 The fid_generation field of this structure will be zero for all non-root callers
407 (effective UID not 0).
408 Equivalent to the ATTR_CMN_OBJID attribute of the parent directory.
409 This identifier need not be persistent across an unmount/mount sequence.
412 On a volume that supports hard links, a multiply linked file has no unique parent.
413 This attribute will return an unspecified parent.
416 For some volume formats this attribute is very expensive to calculate.
421 containing a text encoding hint for
422 the file system object's name.
423 It is included to facilitate the lossless round trip conversion of names between
424 Unicode and traditional Mac OS script encodings.
425 The values are defined in
426 .Aq Pa CarbonCore/TextCommon.h .
427 File systems that do not have an appropriate text encoding value should return
428 kTextEncodingMacUnicode.
429 See DTS Q&A 1173 "File Manager Text Encoding Hints".
434 structure containing the time that the file system object
440 structure containing the time that the file system object
446 structure returned by
452 structure containing the time that the file system object's
453 attributes were last modified.
458 structure returned by
464 structure containing the time that the file system object
470 structure returned by
473 .It ATTR_CMN_BKUPTIME
476 structure containing the time that the file system object was
478 This value is for use by backup utilities.
479 The file system stores but does not interpret the value.
481 .It ATTR_CMN_FNDRINFO
482 (read/write) 32 bytes of data for use by the Finder.
483 Equivalent to the concatenation of a
488 (or, for directories, a
491 .Vt ExtendedFolderInfo
493 These structures are defined in
494 .Aq Pa CarbonCore/Finder.h .
496 This attribute is not byte swapped by the file system.
497 The value of multibyte fields on disk is always big endian.
498 When running on a little endian system (such as Darwin on x86),
499 you must byte swap any multibyte fields.
504 containing the owner of the file system object.
509 structure returned by
515 containing the group of the file system object.
520 structure returned by
523 .It ATTR_CMN_ACCESSMASK
526 containing the access permissions of the file system object.
531 structure returned by
534 .It ATTR_CMN_NAMEDATTRCOUNT
537 containing the number of named attributes of the file system object.
538 No built-in file systems on Mac OS X currently support named attributes.
540 .It ATTR_CMN_NAMEDATTRLIST
543 structure containing a list of named attributes of the file system object.
544 No built-in file systems on Mac OS X currently support named attributes.
545 Because of this, the structure of this attribute's value is not yet defined.
550 containing file flags.
555 structure returned by
557 For more information about these flags, see
561 The order that attributes are placed into the attribute buffer
562 almost invariably matches the order of the attribute mask bit values.
565 If its order was based on its bit position, it would be before
567 .Dv ATTR_CMN_NAMEDATTRCOUNT
569 .Dv ATTR_CMN_NAMEDATTRLIST
571 it is placed in the buffer after them.
573 .It ATTR_CMN_USERACCESS
576 containing the effective permissions of the current user
577 (the calling process's effective UID) for this file system object.
578 You can test for read, write, and execute permission using
589 .Sh VOLUME ATTRIBUTES
591 Volume attributes relate to volumes (that is, mounted file systems).
592 The following volume attributes are defined.
594 .Bl -tag -width ATTR_VOL_ALLOCATIONCLUMP
597 For reasons that are not at all obvious, you must set
601 field if you request any other volume attributes.
602 This does not result in any attribute data being added to the attribute buffer.
607 containing the file system type.
612 structure returned by
614 Generally not a useful value.
616 .It ATTR_VOL_SIGNATURE
619 containing the volume signature word.
620 This value is unique within a given file system type and lets you
621 distinguish between different volume formats handled by the same file system.
623 .Aq Pa CarbonCore/Files.h
629 containing the total size of the volume in bytes.
631 .It ATTR_VOL_SPACEFREE
634 containing the free space on the volume in bytes.
636 .It ATTR_VOL_SPACEAVAIL
639 containing the space, in bytes, on the volume available to non-privileged processes.
640 This is the free space minus the amount of space reserved by the system to prevent critical
641 disk exhaustion errors.
642 Non-privileged programs, like a disk management tool, should use this value to display the
643 space available to the user.
645 .Dv ATTR_VOL_SPACEAVAIL
647 .Dv ATTR_VOL_SPACEFREE
655 .It ATTR_VOL_MINALLOCATION
658 containing the minimum allocation size on the volume in bytes.
659 If you create a file containing one byte, it will consume this much space.
661 .It ATTR_VOL_ALLOCATIONCLUMP
664 containing the allocation clump size on the volume, in bytes.
665 As a file is extended, the file system will attempt to allocate
666 this much space each time in order to reduce fragmentation.
668 .It ATTR_VOL_IOBLOCKSIZE
671 containing the optimal block size when reading or writing data.
676 structure returned by
679 .It ATTR_VOL_OBJCOUNT
682 containing the number of file system objects on the volume.
684 .It ATTR_VOL_FILECOUNT
687 containing the number of files on the volume.
689 .It ATTR_VOL_DIRCOUNT
692 containing the number of directories on the volume.
694 .It ATTR_VOL_MAXOBJCOUNT
697 containing the maximum number of file system objects that can be stored on the volume.
699 .It ATTR_VOL_MOUNTPOINT
702 structure containing the path to the volume's mount point as a
703 UTF-8 encoded, null terminated C string.
704 The attribute data length will not be greater than
710 structure returned by
716 structure containing the name of the volume as a
717 UTF-8 encoded, null terminated C string.
718 The attribute data length will not be greater than
723 This attribute is only read/write if the
724 .Dv VOL_CAP_INT_VOL_RENAME
725 bit is set in the volume capabilities (see below).
728 .It ATTR_VOL_MOUNTFLAGS
731 containing the volume mount flags.
732 This is a copy of the value passed to the
736 when the volume was mounted.
741 structure returned by
744 .It ATTR_VOL_MOUNTEDDEVICE
747 structure that returns the same value as the
751 structure returned by
753 For local volumes this is the path to the device on which the volume is mounted as a
754 UTF-8 encoded, null terminated C string.
755 For network volumes, this is a unique string that identifies the mount.
756 The attribute data length will not be greater than
760 .It ATTR_VOL_ENCODINGSUSED
762 .Vt unsigned long long
763 containing a bitmap of the text encodings used on this volume.
764 For more information about this, see the discussion of
766 in DTS Technote 1150 "HFS Plus Volume Format".
768 .It ATTR_VOL_CAPABILITIES
770 .Vt vol_capabilities_attr_t
771 structure describing the optional features supported by this volume.
772 See below for a discussion of volume capabilities.
774 .It ATTR_VOL_ATTRIBUTES
776 .Vt vol_attributes_attr_t
777 structure describing the attributes supported by this volume.
778 This structure is discussed below, along with volume capabilities.
782 .Sh DIRECTORY ATTRIBUTES
784 The following directory attributes are defined.
786 .Bl -tag -width ATTR_VOL_ALLOCATIONCLUMP
788 .It ATTR_DIR_LINKCOUNT
791 containing the number of file system objects in the directory, including
792 synthetic items such as "." and "..".
793 For historical reasons, you should not always rely on this value being accurate.
795 If you're implementing a volume format on which this is hard to calculate,
796 you should not support this attribute.
797 While it's traditional to return a constant value of 1 in the
801 structure as returned by
803 it's not necessary to do this here because there is a
804 defined way to indicate that you do not support the attribute.
806 .It ATTR_DIR_ENTRYCOUNT
809 containing the number of file system objects in the directory, not including
812 .It ATTR_DIR_MOUNTSTATUS
815 containing flags describing what's mounted on the directory.
816 Currently the only flag defined is
817 .Dv DIR_MNTSTATUS_MNTPOINT,
818 which indicates that there is a file system mounted on this directory.
819 Due to a bug (r. 3502822), this flag is never set on current system.
825 The following file attributes are defined.
827 .Bl -tag -width ATTR_VOL_ALLOCATIONCLUMP
829 .It ATTR_FILE_LINKCOUNT
832 containing the number of hard links to this file.
837 structure returned by
840 .It ATTR_FILE_TOTALSIZE
843 containing the total number of bytes in all forks of the file (the logical size).
845 .It ATTR_FILE_ALLOCSIZE
848 containing a count of the bytes on disk used by all of the file's forks (the physical size).
850 .It ATTR_FILE_IOBLOCKSIZE
853 containing the optimal block size when reading or writing this file's data.
855 .It ATTR_FILE_CLUMPSIZE
858 containing the allocation clump size for this file, in bytes.
859 As the file is extended, the file system will attempt to allocate
860 this much space each time in order to reduce fragmentation.
861 This value applies to the data fork.
863 .It ATTR_FILE_DEVTYPE
866 containing the device type for a special device file.
871 structure returned by
874 .It ATTR_FILE_FILETYPE
877 that whose value is reserved.
878 Clients should ignore its value.
879 New volume format implementations should not support this attribute.
881 .It ATTR_FILE_FORKCOUNT
884 containing the number of forks in the file.
885 No built-in file systems on Mac OS X currently support forks other
886 than the data and resource fork.
888 .It ATTR_FILE_FORKLIST
891 structure containing a list of named forks of the file.
892 No built-in file systems on Mac OS X currently support forks
893 other than the data and resource fork.
894 Because of this, the structure of this attribute's value is not yet defined.
896 .It ATTR_FILE_DATALENGTH
899 containing the length of the data fork in bytes (the logical size).
901 .It ATTR_FILE_DATAALLOCSIZE
904 containing a count of the bytes on disk used by the data fork (the physical size).
906 .It ATTR_FILE_DATAEXTENTS
909 array for the data fork.
910 The array contains eight
912 structures which represent the first
913 eight extents of the fork.
915 This attributes exists for compatibility reasons.
916 New clients should not use this attribute.
917 Rather, they should use the
923 In current implementations the value may not be entirely accurate for
924 a variety of reasons.
926 .It ATTR_FILE_RSRCLENGTH
929 containing the length of the resource fork in bytes (the logical size).
931 .It ATTR_FILE_RSRCALLOCSIZE
934 containing a count of the bytes on disk used by the resource fork (the physical size).
936 .It ATTR_FILE_RSRCEXTENTS
939 array for the resource fork.
940 The array contains eight
942 structures which represent the first
943 eight extents of the fork.
946 .Dv ATTR_FILE_DATAEXTENTS .
952 Fork attributes relate to the actual data in the file,
953 which can be held in multiple named contiguous ranges, or forks.
954 The following fork attributes are defined.
956 .Bl -tag -width ATTR_VOL_ALLOCATIONCLUMP
958 .It ATTR_FORK_TOTALSIZE
961 containing the length of the fork in bytes (the logical size).
963 .It ATTR_FORK_ALLOCSIZE
966 containing a count of the bytes on disk used by the fork (the physical size).
971 Fork attributes are not properly implemented by any current Mac OS X
972 volume format implementation.
973 We strongly recommend that client programs do not request fork attributes.
974 If you are implementing a volume format, you should not support these attributes.
976 .Sh VOLUME CAPABILITIES
978 .\" vol_capabilities_attr_t
980 Not all volumes support all features. The
981 .Dv ATTR_VOL_CAPABILITIES
983 .Vt vol_capabilities_attr_t
984 structure (shown below) that indicates which features are supported by the volume.
987 typedef u_int32_t vol_capabilities_set_t[4];
990 #define VOL_CAPABILITIES_FORMAT 0
991 #define VOL_CAPABILITIES_INTERFACES 1
992 #define VOL_CAPABILITIES_RESERVED1 2
993 #define VOL_CAPABILITIES_RESERVED2 3
996 typedef struct vol_capabilities_attr {
997 vol_capabilities_set_t capabilities;
998 vol_capabilities_set_t valid;
999 } vol_capabilities_attr_t;
1003 The structure contains two fields,
1007 Each consists of an array of four elements.
1008 The arrays are indexed by the following values.
1010 .Bl -tag -width VOL_CAP_FMT_PERSISTENTOBJECTIDS
1012 .It VOL_CAPABILITIES_FORMAT
1013 This element contains information about the volume format.
1015 .Dv VOL_CAP_FMT_PERSISTENTOBJECTIDS
1018 .It VOL_CAPABILITIES_INTERFACES
1019 This element contains information about which optional functions are
1020 supported by the volume format implementation.
1022 .Dv VOL_CAP_INT_SEARCHFS
1025 .It VOL_CAPABILITIES_RESERVED1
1027 A file system implementation should set this element to zero.
1028 A client program should ignore this element.
1030 .It VOL_CAPABILITIES_RESERVED2
1032 A file system implementation should set this element to zero.
1033 A client program should ignore this element.
1040 field contains bit sets that indicate which flags are known to the volume format
1042 Each bit indicates whether the contents of the corresponding bit in the
1049 field contains bit sets that indicate whether a particular feature is implemented
1050 by this volume format.
1053 The following bits are defined in the first element (indexed by
1054 .Dv VOL_CAPABILITIES_FORMAT )
1060 .Vt vol_capabilities_attr_t
1063 .Bl -tag -width VOL_CAP_FMT_PERSISTENTOBJECTIDS
1065 .It VOL_CAP_FMT_PERSISTENTOBJECTIDS
1066 If this bit is set the volume format supports persistent object identifiers
1067 and can look up file system objects by their IDs.
1069 .Dv ATTR_CMN_OBJPERMANENTID
1070 for details about how to obtain these identifiers.
1072 .It VOL_CAP_FMT_SYMBOLICLINKS
1073 If this bit is set the volume format supports symbolic links.
1075 .It VOL_CAP_FMT_HARDLINKS
1076 If this bit is set the volume format supports hard links.
1078 .It VOL_CAP_FMT_JOURNAL
1079 If this bit is set the volume format supports a journal used to
1080 speed recovery in case of unplanned restart (such as a power outage
1082 This does not necessarily mean the volume is actively using a journal.
1084 Introduced with Darwin 7.0 (Mac OS X version 10.3).
1086 .It VOL_CAP_FMT_JOURNAL_ACTIVE
1087 If this bit is set the volume is currently using a journal for
1088 speedy recovery after an unplanned restart.
1089 This bit can be set only if
1090 .Dv VOL_CAP_FMT_JOURNAL
1093 Introduced with Darwin 7.0 (Mac OS X version 10.3).
1095 .It VOL_CAP_FMT_NO_ROOT_TIMES
1096 If this bit is set the volume format does not store reliable times for
1097 the root directory, so you should not depend on them to detect changes,
1098 identify volumes across unmount/mount, and so on.
1100 Introduced with Darwin 7.0 (Mac OS X version 10.3).
1102 .It VOL_CAP_FMT_SPARSE_FILES
1103 If this bit is set the volume format supports sparse files,
1104 that is, files which can have 'holes' that have never been written
1105 to, and thus do not consume space on disk.
1106 A sparse file may have an allocated size on disk that is less than its logical length (that is,
1107 .Dv ATTR_FILE_ALLOCSIZE
1109 .Dv ATTR_FILE_TOTALSIZE ).
1112 Introduced with Darwin 7.0 (Mac OS X version 10.3).
1114 .It VOL_CAP_FMT_ZERO_RUNS
1115 For security reasons, parts of a file (runs) that have never been
1116 written to must appear to contain zeroes.
1117 When this bit is set, the volume keeps track of allocated but unwritten
1118 runs of a file so that it can substitute zeroes without actually
1119 writing zeroes to the media.
1120 This provides performance similar to sparse files, but not the space savings.
1122 Introduced with Darwin 7.0 (Mac OS X version 10.3).
1124 .It VOL_CAP_FMT_CASE_SENSITIVE
1125 If this bit is set the volume format treats upper and lower case
1126 characters in file and directory names as different.
1127 Otherwise an upper case character is equivalent to a lower case character,
1128 and you can't have two names that differ solely in the case of
1131 Introduced with Darwin 7.0 (Mac OS X version 10.3).
1133 .It VOL_CAP_FMT_CASE_PRESERVING
1134 If this bit is set the volume format preserves the case of
1135 file and directory names.
1136 Otherwise the volume may change the case of some characters
1137 (typically making them all upper or all lower case).
1139 .Dv VOL_CAP_FMT_CASE_SENSITIVE
1141 .Dv VOL_CAP_FMT_CASE_PRESERVING .
1143 Introduced with Darwin 7.0 (Mac OS X version 10.3).
1145 .It VOL_CAP_FMT_FAST_STATFS
1146 This bit is used as a hint to upper layers (specifically the Carbon File Manager) to
1149 is fast enough that its results need not be cached by the caller.
1150 A volume format implementation that caches the
1152 information in memory should set this bit.
1153 An implementation that must always read from disk or always perform a network
1154 transaction to satisfy
1156 should not set this bit.
1158 Introduced with Darwin 7.0 (Mac OS X version 10.3).
1160 .It VOL_CAP_FMT_2TB_FILESIZE
1161 If this bit is set the volume format supports file
1162 sizes upto 2TB. This bit does not necessarily mean that the file
1163 system does not support file size more than 2TB. This bit does
1164 not mean that the currently available space on the volume is 2TB.
1166 Introduced with Darwin 8.0 (Mac OS X version 10.4).
1171 The following bits are defined in the second element (indexed by
1172 .Dv VOL_CAPABILITIES_INTERFACES )
1178 .Vt vol_capabilities_attr_t
1181 .Bl -tag -width VOL_CAP_FMT_PERSISTENTOBJECTIDS
1183 .It VOL_CAP_INT_SEARCHFS
1184 If this bit is set the volume format implementation supports
1187 .It VOL_CAP_INT_ATTRLIST
1188 If this bit is set the volume format implementation supports
1193 .It VOL_CAP_INT_NFSEXPORT
1194 If this bit is set the volume format implementation allows this volume to be exported via NFS.
1196 .It VOL_CAP_INT_READDIRATTR
1197 If this bit is set the volume format implementation supports
1198 .Xr getdirentriesattr 2 .
1200 .It VOL_CAP_INT_EXCHANGEDATA
1201 If this bit is set the volume format implementation supports
1202 .Xr exchangedata 2 .
1204 Introduced with Darwin 7.0 (Mac OS X version 10.3).
1206 .It VOL_CAP_INT_COPYFILE
1207 If this bit is set the volume format implementation supports the (private and undocumented)
1208 copyfile() function.
1210 Introduced with Darwin 7.0 (Mac OS X version 10.3).
1212 .It VOL_CAP_INT_ALLOCATE
1213 If this bit is set the volume format implementation supports the
1218 Introduced with Darwin 7.0 (Mac OS X version 10.3).
1220 .It VOL_CAP_INT_VOL_RENAME
1221 If this bit is set the volume format implementation allows you to
1222 modify the volume name using
1225 Introduced with Darwin 7.0 (Mac OS X version 10.3).
1227 .It VOL_CAP_INT_ADVLOCK
1228 If this bit is set the volume format implementation supports
1229 advisory locking, that is, the
1237 Introduced with Darwin 7.0 (Mac OS X version 10.3).
1239 .It VOL_CAP_INT_FLOCK
1240 If this bit is set the volume format implementation supports
1251 Introduced with Darwin 7.0 (Mac OS X version 10.3).
1256 .\" vol_attributes_attr_t
1258 A volume can also report which attributes it supports.
1259 This information is returned by the
1260 .Dv ATTR_VOL_ATTRIBUTES
1261 attribute, which returns a
1262 .Vt vol_attributes_attr_t
1263 structure (shown below).
1266 typedef struct attribute_set {
1267 attrgroup_t commonattr; /* common attribute group */
1268 attrgroup_t volattr; /* volume attribute group */
1269 attrgroup_t dirattr; /* directory attribute group */
1270 attrgroup_t fileattr; /* file attribute group */
1271 attrgroup_t forkattr; /* fork attribute group */
1275 typedef struct vol_attributes_attr {
1276 attribute_set_t validattr;
1277 attribute_set_t nativeattr;
1278 } vol_attributes_attr_t;
1284 field consists of a number of bit sets that indicate whether an attribute is
1285 supported by the volume format implementation.
1288 is similar except that the bit sets indicate whether an attribute is supported
1289 natively by the volume format.
1290 An attribute is supported natively if the volume format implementation does not have to do
1291 any complex conversions to access the attribute.
1292 For example, a volume format might support persistent object identifiers, but
1293 doing so requires a complex table lookup that is not part of the core volume
1296 .Dv ATTR_VOL_ATTRIBUTES
1297 attribute would return
1298 .Dv ATTR_CMN_OBJPERMANENTID
1302 .Vt vol_attributes_attr_t ,
1308 Upon successful completion a value of 0 is returned.
1309 Otherwise, a value of -1 is returned and
1311 is set to indicate the error.
1314 Not all volumes support
1316 The best way to test whether a volume supports this function is to
1317 simply call it and check the error result.
1321 if it is not supported on a particular volume.
1326 function has been undocumented for more than two years.
1327 In that time a number of volume format implementations have been created without
1328 a proper specification for the behaviour of this routine.
1329 You may encounter volume format implementations with slightly different
1330 behaviour than what is described here.
1331 Your program is expected to be tolerant of this variant behaviour.
1334 If you're implementing a volume format that supports
1336 you should be careful to support the behaviour specified by this document.
1344 The volume does not support
1348 A component of the path prefix is not a directory.
1350 .It Bq Er ENAMETOOLONG
1351 A component of a path name exceeded
1353 characters, or an entire path name exceeded
1358 The file system object does not exist.
1361 Search permission is denied for a component of the path prefix.
1364 Too many symbolic links were encountered in translating the pathname.
1371 points to an invalid address.
1379 .Dv ATTR_BIT_MAP_COUNT .
1382 You requested an invalid attribute.
1385 You requested an attribute that is not supported for this file system object.
1388 You requested volume attributes and directory or file attributes.
1391 You requested volume attributes but
1393 does not reference the root of the volume.
1396 The volume is read-only but must be modified in order to return this attribute.
1399 An I/O error occurred while reading from or writing to the file system.
1405 If you request any volume attributes, you must set
1409 field, even though it generates no result in the attribute buffer.
1412 The order that attributes are stored in the attribute buffer almost
1413 invariably matches the order of attribute mask bit values.
1416 (0x00000001) comes before
1418 (0x00000002) because its value is smaller.
1419 However, you can not rely on this ordering because there is one key exception:
1422 .Dv ATTR_CMN_NAMEDATTRCOUNT
1424 .Dv ATTR_CMN_NAMEDATTRLIST
1425 pair, even though its bit position indicates that it should come before.
1426 This is due to a bug in an early version of Mac OS X that can't be fixed for
1427 binary compatibility reasons.
1428 When ordering attributes, you should always use the order in which they
1429 are described above.
1432 For more caveats, see also the compatibility notes above.
1436 The following code prints the file type and creator of a file,
1437 assuming that the volume supports the required attributes.
1443 #include <sys/attr.h>
1444 #include <sys/errno.h>
1446 #include <sys/vnode.h>
1449 typedef struct attrlist attrlist_t;
1452 struct FInfoAttrBuf {
1453 unsigned long length;
1454 fsobj_type_t objType;
1455 char finderInfo[32];
1457 typedef struct FInfoAttrBuf FInfoAttrBuf;
1460 static int FInfoDemo(const char *path)
1463 attrlist_t attrList;
1464 FInfoAttrBuf attrBuf;
1467 memset(&attrList, 0, sizeof(attrList));
1468 attrList.bitmapcount = ATTR_BIT_MAP_COUNT;
1469 attrList.commonattr = ATTR_CMN_OBJTYPE | ATTR_CMN_FNDRINFO;
1472 err = getattrlist(path, &attrList, &attrBuf, sizeof(attrBuf), 0);
1479 assert(attrBuf.length == sizeof(attrBuf));
1482 printf("Finder information for %s:\en", path);
1483 switch (attrBuf.objType) {
1485 printf("file type = '%.4s'\en", &attrBuf.finderInfo[0]);
1486 printf("file creator = '%.4s'\en", &attrBuf.finderInfo[4]);
1489 printf("directory\en");
1492 printf("other object type, %d\en", attrBuf.objType);
1503 The following code is an alternative implementation that uses nested structures
1504 to group the related attributes.
1511 #include <sys/attr.h>
1512 #include <sys/errno.h>
1514 #include <sys/vnode.h>
1517 typedef struct attrlist attrlist_t;
1520 struct FInfo2CommonAttrBuf {
1521 fsobj_type_t objType;
1522 char finderInfo[32];
1524 typedef struct FInfo2CommonAttrBuf FInfo2CommonAttrBuf;
1527 struct FInfo2AttrBuf {
1528 unsigned long length;
1529 FInfo2CommonAttrBuf common;
1531 typedef struct FInfo2AttrBuf FInfo2AttrBuf;
1534 static int FInfo2Demo(const char *path)
1537 attrlist_t attrList;
1538 FInfo2AttrBuf attrBuf;
1541 memset(&attrList, 0, sizeof(attrList));
1542 attrList.bitmapcount = ATTR_BIT_MAP_COUNT;
1543 attrList.commonattr = ATTR_CMN_OBJTYPE | ATTR_CMN_FNDRINFO;
1546 err = getattrlist(path, &attrList, &attrBuf, sizeof(attrBuf), 0);
1553 assert(attrBuf.length == sizeof(attrBuf));
1556 printf("Finder information for %s:\en", path);
1557 switch (attrBuf.common.objType) {
1560 "file type = '%.4s'\en",
1561 &attrBuf.common.finderInfo[0]
1564 "file creator = '%.4s'\en",
1565 &attrBuf.common.finderInfo[4]
1569 printf("directory\en");
1573 "other object type, %d\en",
1574 attrBuf.common.objType
1586 The following example shows how to deal with variable length attributes.
1587 It assumes that the volume specified by
1589 supports the necessary attributes.
1596 #include <sys/attr.h>
1597 #include <sys/errno.h>
1599 #include <sys/vnode.h>
1602 typedef struct attrlist attrlist_t;
1606 unsigned long length;
1607 unsigned long fileCount;
1608 unsigned long dirCount;
1609 attrreference_t mountPointRef;
1610 attrreference_t volNameRef;
1611 char mountPointSpace[MAXPATHLEN];
1612 char volNameSpace[MAXPATHLEN];
1614 typedef struct VolAttrBuf VolAttrBuf;
1617 static int VolDemo(const char *path)
1620 attrlist_t attrList;
1624 memset(&attrList, 0, sizeof(attrList));
1625 attrList.bitmapcount = ATTR_BIT_MAP_COUNT;
1626 attrList.volattr = ATTR_VOL_INFO
1627 | ATTR_VOL_FILECOUNT
1629 | ATTR_VOL_MOUNTPOINT
1633 err = getattrlist(path, &attrList, &attrBuf, sizeof(attrBuf), 0);
1640 assert(attrBuf.length > offsetof(VolAttrBuf, mountPointSpace));
1641 assert(attrBuf.length <= sizeof(attrBuf));
1644 printf("Volume information for %s:\en", path);
1645 printf("ATTR_VOL_FILECOUNT: %lu\en", attrBuf.fileCount);
1646 printf("ATTR_VOL_DIRCOUNT: %lu\en", attrBuf.dirCount);
1648 "ATTR_VOL_MOUNTPOINT: %.*s\en",
1649 (int) attrBuf.mountPointRef.attr_length,
1650 ( ((char *) &attrBuf.mountPointRef)
1651 + attrBuf.mountPointRef.attr_dataoffset )
1654 "ATTR_VOL_NAME: %.*s\en",
1655 (int) attrBuf.volNameRef.attr_length,
1656 ( ((char *) &attrBuf.volNameRef)
1657 + attrBuf.volNameRef.attr_dataoffset )
1671 .Xr exchangedata 2 ,
1673 .Xr getdirentriesattr 2 ,
1683 function call appeared in Darwin 1.3.1 (Mac OS X version 10.0).