Technical data

ZFS and UNIX/POSIX Compliance Issues
ZFS is designed to be a POSIX compliant le system and in most situations, ZFS is POSIX
compliant. However, two edge case conditions exist when ZFS does not meet the POSIX
compliance tests:
1. Updating ZFS les system capacity statistics.
2. Modifying existing data with a 100 percent full le system.
Related CRs:
6362314
6362156
6361650
6343113
6343039
fdisk -E Can Sweep Disk Used by ZFS Without
Warning (6412771)
If you use the fdisk -E command to modify a disk that is used by a ZFS storage pool, the pool
becomes unusable and might cause an I/O failure or system panic.
Workaround:
Do not use the fdisk command to modify a disk that is used by a ZFS storage pool. If you need
to access a disk that is used by a ZFS storage pool, use the format utility. In general, disks that
are in use by le systems should not be modied.
ZFS and Third-Party Backup Product Issues
The following are the issues with the Veritas NetBackup and Brightstor ARCserve Backup
products.
Veritas NetBackup Does Not Back Up and Preserve FilesWith
ZFS/NFSv4 ACLs (6352899)
The Veritas NetBackup product can be used to back up ZFS les, and this conguration is
supported. However, this product does not currently support backing up or restoring
NFSv4-style ACL information from ZFS les. Traditional permission bits and other le
attributes are correctly backed up and restored.
If a user tries to back up or restore ZFS les, the NFSv4-style ACL information from ZFS les is
silently dropped. There is no error message indicating that the ACL information from ZFS les
has been dropped.
File Systems
Solaris 10 5/08 Release Notes • April 200858