File Systems

The following file system bugs apply to this Oracle Solaris 10 release.

ZFS Dynamic LUN Expansion Restriction (6241086)

A logical unit number (LUN) does not expand dynamically in an existing ZFS storage pool. To dynamically expand a LUN in an existing ZFS storage pool by using the autoexpand property or the zpool online -e command, you must contact My Oracle Support for the required patches.

Workaround: Consider the following workarounds:

• Attach a larger LUN to the pool by using the zpool attach command. After the larger LUN is resilvered, detach the smaller LUN by using the zpool detach command.

• Replace the smaller LUN with a larger LUN by using the zpool replace command.

The config/local_only Property in sendmail Must Not Be Set to true (6970172)

The sendmail patch 142436–03 and its revisions 04 to 08, modifies the config/local_only property to true.

$ svcprop -p config/local_only smtp:sendmail
true

This modification allows sendmail to accept requests only from the local host.

Workaround: After adding patch 142436–03 or its revisions 04 to 08, in order for sendmail to accept requests from other hosts, make the following changes:

1. Reset the config/local_only property to false.

   # svccfg -s svc:/network/smtp:sendmail setprop config/local_only=false

2. Refresh and restart the sendmail service.

   # svcadm refresh smtp:sendmail
   # svcadm restart smtp:sendmail

x86: ata Driver Timeouts During Boot (6586621)

ata driver timeouts might occur during system boot on Intel multiprocessor systems. These timeouts occur when the root device is on a drive with the HBA controller bound to the legacy ata driver. These timeouts lead to a momentary hang, a hard hang, or a panic during system boot with console messages similar to the following:

scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci-ide@1f,2/ide@0 (ata0):
        timeout: reset bus, target=0 lun=0
scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci-ide@1f,2/ide@0 (ata0):
        timeout: early timeout, target=0 lun=0
gda: [ID 107833 kern.warning] WARNING: /pci@0,0/pci-ide@1f,2/ide@0/cmdk@0,0 (Disk0):
        Error for command 'read sector'   Error Level: Informational
gda: [ID 107833 kern.notice]           Sense Key: aborted command
gda: [ID 107833 kern.notice]           Vendor 'Gen-ATA ' error code: 0x3
gda: [ID 107833 kern.warning] WARNING: /pci@0,0/pci-ide@1f,2/ide@0/cmdk@0,0 (Disk0):
        Error for command 'read sector'   Error Level: Informational
gda: [ID 107833 kern.notice]           Sense Key: aborted command
gda: [ID 107833 kern.notice]           Vendor 'Gen-ATA ' error code: 0x3
scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci-ide@1f,2/ide@0 (ata0):
        timeout: abort request, target=0 lun=0
scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci-ide@1f,2/ide@0 (ata0):
        timeout: abort device, target=0 lun=0
scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci-ide@1f,2/ide@0 (ata0):
        timeout: reset target, target=0 lun=0
scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci-ide@1f,2/ide@0 (ata0):
        timeout: reset bus, target=0 lun=0
scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci-ide@1f,2/ide@0 (ata0):
        timeout: early timeout, target=0 lun=0
gda: [ID 107833 kern.warning] WARNING: /pci@0,0/pci-ide@1f,2/ide@0/cmdk@0,0 (Disk0):
        Error for command 'read sector'   Error Level: Informational
gda: [ID 107833 kern.notice]           Sense Key: aborted command
gda: [ID 107833 kern.notice]           Vendor 'Gen-ATA ' error code: 0x3
gda: [ID 107833 kern.warning] WARNING: /pci@0,0/pci-ide@1f,2/ide@0/cmdk@0,0 (Disk0):

Workaround: Choose one of the following workarounds.

• Workaround 1: Enable AHCI in BIOS if available on the system. Enabling this setting requires a reinstallation of the Oracle Solaris OS.

• Workaround 2: Install the Oracle Solaris OS on a disk on a controller that does not use the ata driver.

• Workaround 3: Disable MP in the BIOS setup so that a single processor is active.

• Workaround 4: Disable MP in the Oracle Solaris OS so that a single processor is active. Perform the following steps from the GRUB menu:

  1. Type e to edit your selected entry.

  2. Navigate to the line that begins with “kernel.”

  3. Type e to switch to GRUB edit mode.

  4. Append -kd to the line.

  5. Press Enter to accept the change.

  6. Type b to boot the selected entry.

  7. At the kbmd prompt, type the following command:

     use_mp/W 0 :c

  8. If you are performing a system boot, proceed to Step 10. Otherwise, install the Solaris 10 10/09 software.

  9. At the end of the installation, reboot the system. Repeat steps 1 through 7.

  10. To make this change permanent so that the above steps do not need to be repeated for subsequent boots, do the following:

      1. Become the superuser when the system boot is completed.

      2. Open the /etc/system file.

      3. Add the following line:

         set use_mp = 0

• Workaround 5: Disable the microcode update. Type the following command:

  # mv /platform/i86pc/ucode /platform/i86pc/ucode.disabled

  The microcode update can be invoked manually after the system is up by typing the following command:

  # ucodeadm -u /platform/i86pc/ucode.disabled/intel-ucode.txt

zoneadm install Command Fails With a ZFS Legacy Mount (6449301)

If a non-global zone is initially configured with a ZFS file system to be mounted with the add fs subcommand and the configuration specifies mountpoint=legacy, the subsequent zone installation fails. The following error message is displayed:

ERROR: No such file or directory:
cannot mount </zones/path/root/usr/local> in non-global zone to install:
the source block device or directory </path/local> cannot be accessed

Workaround: Add access to a ZFS file system after installing the non-global zone.

ZFS and UNIX/POSIX Compliance Issues

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.

Related CRs:

• 6362314

• 6362156

• 6361650

fdisk -E Command 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 file systems should not be modified.

BrightStor ARCserve Backup Client Agent for UNIX (Solaris) and ZFS Support Issue

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.

ZFS GUI Should Check for /usr/lib/embedded_su Patch at the Beginning of Each Wizard (6326334)

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.

Failure to Synchronize File System on Panic (6250422)

If a host panics when file system I/O is being sent to a target that is connected by using the Oracle Solaris iSCSI software initiator, the I/O might not be able to flush or sync to the target device. This inability to flush or sync might cause file system corruption. No error message is displayed.

Workaround:

Use a journaling file system such as UFS. Starting with the Oracle Solaris 10 OS, UFS logging is enabled by default. For more information about UFS, see What’s New in Oracle Solaris File Systems? in System Administration Guide: Devices and File Systems.

Upgrading From Some Oracle Solaris 10 Releases Requires Remounting of File Systems

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 Functions Might Work Incorrectly

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:

• acl()

• facl()

• getfacl

• setfacl

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.

System Crash Dump Fails on Devices Greater Than 1 TByte in Size (6214480)

A system cannot generate a crash dump on a partition that is equal to or greater than 1 Tbyte in size. If a partition of this size is on a system, the following might occur after the system boots following a system panic:

• The system does not save the dump.

• The following message is displayed:

  0% done: 0 pages dumped, compression ratio 0.00, dump failed: error 6

Workaround: Configure the size of your system's dump device to less than 1 Tbyte.