rw-r-r-+ 1 root staff 0 22 Mar 17:23 acl-testĭrwxr-xr-x+ 2 root staff 68 22 Mar 17:23 acl-test-dirĪdmin$ ls -Plde /Volumes/Src/80-access-control-lists/* xattr-testĬom.apple.FinderInfo 1 root staff 0 22 Mar 17:23 xattr-testĪdmin$ ls /Volumes/Src/80-access-control-lists/ ief 1 root staff 0 22 Mar 17:23 xattr-testĬom.apple.FinderInfo 2 root staff 2 22 Mar 17:23 dir-with-xattrsĬom.apple.FinderInfo 1 root staff 12 22 Mar 17:23 symlink-with-xattrs ->. Mamma.mia 1 root staff 12 22 Mar 17:23 symlink-with-xattrs ->. ĭrwxr-xr-x 22 admin staff 816 22 Mar 17:23 2 root staff 68 22 Mar 17:23 dir-with-xattrs rw-r-r- 1 root staff 0 22 Mar 17:23 file-with-flagsĪdmin$ /usr/bin/stat -f '%f' /Volumes/Src/60-bsd-flags/dir-with-flagsĪdmin$ /usr/bin/stat -f '%f' /Volumes/Src/60-bsd-flags/file-with-flagsĬom.apple.FinderInfo 2 admin staff 2 22 Mar 17:23 dir-with-flagsĬom.apple.FinderInfo 1 root staff 0 22 Mar 17:23 file-with-flagsĪdmin$ /usr/bin/stat -f '%f' /ztank/60-bsd-flags/dir-with-flagsĪdmin$ /usr/bin/stat -f '%f' /ztank/60-bsd-flags/file-with-flagsĪdmin$ ls /Volumes/Src/70-extended-attrs/ĭrwxr-xr-x 5 root staff 170 22 Mar 17:23. ĭrwxr-xr-x 2 root staff 68 22 Mar 17:23 dir-with-flags Ĭom.apple.FinderInfo 1 root staff 0 creation-date-testĭrwxr-xr-x 4 root staff 136 22 Mar 17:23. rw-r-r- 1 root staff 0 creation-date-testĬom.apple.FinderInfo 20 admin staff 23 22 Mar 17:31. Here are the details of the failed copy tests between HFS+ volume and the ZFS tank:Ĭode: Select all admin$ ls /Volumes/Src/50-creation-date/ĭrwxr-xr-x 3 root staff 102 22 Mar 17:23. bbouncer verify -d /Volumes/Src/ /Volumes/Dst/ Verification result looks as follows:Ĭode: Select all admin$ sudo. FAIL (Important)Ĭross-check with very same software, but using a jHFS+ disk image as destination. bbouncer verify -d /Volumes/Src/ /ztank/ ZFS volume created on external HDD as follows (full flag list at end of post):Ĭode: Select all sudo zpool create -f -o ashift=12 -O atime=off -O casesensitivity=insensitive -O normalization=formD ztank /dev/disk1s3Ĭopy-test between a journaled HFS+ volume (diskimage) using ChronoSync to the external harddisk which was formed as shown above with zfs resulted into the following verification result (note the FAILs on extended attributes, bsd flags and ACL tests):Ĭode: Select all admin$ sudo. external 2.5'' Seagate HDD via Firewire-400 connectionĪll software run with admin / sudo rights The ACL and bsd flags are quite mungled though once one goes through the HFS+ -> ZFS -> HFS+ copy chain. So is there a mechanism in OpenZFS which returns a 'default' FinderInfo object to certain API calls even if there is no FinderInfo stored with the underlying file? Once I copy the files back from zfs to another HFS+ volume, only those FinderInfos are copied which were already there before. I have further experimented with this and it seems that the additional FinderInfo attribute, which I see on the zfs volume, is only transient: The main issue (for me) is that there are apparently extended attributes are added to each file that is copied onto the ZFS volume! The result was a bit puzzling: ZFS shows quite some problems to correctly handle extended attributes, bsd flags and access control lists. I have run some copy tests between a jHFS+ and an OpenZFS volume to check how well OSX's meta-data is support.
0 Comments
Leave a Reply. |