The hdiutil man page states: > OS X 10.5 introduced sparse bundle images which compact quickly but are not > recognized by previous OS versions. OS X 10.6 removed support for attaching > SPARSEBUNDLE images from network file servers that don't support F_FULLFSYNC.
Up to and including Mavericks, I cannot attach a sparsebundle disk image on, for example, an SMB sharepoint because it lacks support for F_FULLFSYNC: ***** Mavericks:~ $ sw_vers -productVersion 10.9.2 Mavericks:~ $ mount ... //mike@baltar.local/Backup on /Volumes/Backup (smbfs, nodev, nosuid, mounted by mike) Mavericks:~ $ ~/fullfsync /Volumes/Backup fcntl(fd, F_FULLFSYNC, 1) returned -1, errno: 45 /Volumes/Backup does not support F_FULLFSYNC Mavericks:~ $ hdiutil attach /Volumes/Backup/Macintosh.sparsebundle hdiutil: attach failed - Resource temporarily unavailable ***** Yosemite, however, allows the attach, on the same filesystem: ***** Yosemite:~ $ sw_vers -productVersion 10.10.1 Yosemite:~ $ mount ... //mike@baltar.local/Backup on /Volumes/Backup (smbfs, nodev, nosuid, mounted by mike) Yosemite:~ $ ./fullfsync /Volumes/Backup fcntl(fd, F_FULLFSYNC, 1) returned -1, errno: 45 /Volumes/Backup does not support F_FULLFSYNC Yosemite:~ $ hdiutil attach /Volumes/Backup/Macintosh.sparsebundle /dev/disk4 /Volumes/Macintosh ***** I don't see any changes in the hdiutil man page or any other Yosemite documentation that would suggest that sparsebundle disk images can now be used on filesystems that do not support F_FULLFSYNC. Is this a bug in Yosemite, or a change in policy for disk images? Mike
_______________________________________________ Do not post admin requests to the list. They will be ignored. Filesystem-dev mailing list (Filesystem-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/filesystem-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com