|Skip Navigation Links|
|Exit Print View|
|Oracle Solaris 10 1/13 Release Notes Oracle Solaris 10 1/13 Information Library|
The following file system issues and bugs apply to this Oracle Solaris 10 release.
If the system is not shutdown properly, data integrity issues might be encountered. For more information, see InfoDoc 1502451.1 on My Oracle Support.
Workaround: For information about the workaround, see InfoDoc 1502446.1 on My Oracle Support.
If your system reboots continuously because of a ZFS storage pool with corrupted space map entries, send a system crash dump to Oracle support for root cause analysis.
The initial or subsequent panic strings begin as follows:
zfs: freeing free segment zfs: allocating allocated segment
Any attempt to import and mount the problem pool causes the system to panic.
Workaround: Identify the problem pool and import the pool in read-only mode.
Stop the system and boot the system with the milestone=none option.
For SPARC, type the following command:
ok boot -m milestone=none
For x86, add the milestone option to the appropriate GRUB entry:
Immediately, rename the zpool.cache file to prevent the system from importing non-root pools.
# mv /etc/zfs/zpool.cache /etc/zfs/zpool.hold
Do not use any ZFS commands that cause the pool information to be loaded.
Reboot the system.
Import each pool one at a time to determine the problem pool.
Import the problem pool in read-only mode.
# zpool import -o readonly=on poolname
For information, see InfoDoc 1497293.1 on My Oracle Support.
ZFS is designed to be a POSIX compliant file system and, in most situations, ZFS is POSIX compliant. However, ZFS does not meet the POSIX compliance tests under the following conditions:
Updating ZFS files system capacity statistics.
Modifying existing data with a 100 percent full file system.
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 file systems should not be modified.
The BrightStor ARCserve Backup (BAB) Client Agent for UNIX (Solaris) can be used to back up and restore ZFS files.
However, ZFS NFSv4-style ACLs are not preserved during backup. Traditional UNIX file permissions and attributes are preserved.
Workaround: To preserve ZFS files with NFSv4-style ACLs, use the tar command with the -p option or the cpio command with the -P option to write the ZFS files to a file. Then, use BAB to back up the tar or cpio archive.
If you add the SUNWzfsg package from a Solaris 10 10/09 release to a system that runs a release prior to the Solaris 10 6/06 release that does not have the embedded_su patch, the ZFS Administration application wizards are not fully functional.
If you attempt to run the ZFS Administration application on a system without the embedded_su patch, you will only be able to browse your ZFS configuration. The following error message is displayed:
/usr/lib/embedded_su: not found
Workaround: Add the embedded_su patch (119574-02) to the system that runs a release prior to the Solaris 10 6/06 release.
For all Oracle Solaris 10 releases, after you upgrade an NFSv4 server, your programs might encounter EACCES errors. Furthermore, directories might erroneously appear to be empty.
To prevent these errors, unmount and then remount the client file systems. If the unmounting fails, you might need to forcibly unmount the file system by using the umount -f command. Alternatively, you can reboot the client.
NFSv4 access control list (ACL) functions might work incorrectly if clients and servers in the network are installed with different Oracle Solaris 10 releases. The affected ACL functions and command-line utilities that use these functions are the following:
For more information about these functions and utilities, see their respective man pages.
For example, errors might be observed in a network that includes the following configuration:
A client that is running Oracle Solaris 10 Beta software
A server that is running Oracle Solaris 10 software
The following table illustrates the results of the ACL functions in client-server configurations with different Oracle Solaris 10 releases.
Workaround: For the NFSv4 ACL functionality to work properly, perform a full installation of the Oracle Solaris 10 OS on both the server and the client.