This section describes file system issues in the Oracle Solaris 11.4 release.
If the SMB service is disabled or stopped while Windows client sessions are active, the system might panic.
Workaround: Do not shutdown the SMB service while any SMB client session is still active. If you are using the SMB service on your Oracle Solaris system, you might want to wait until Oracle Solaris 11.4 SRU 1 is available to upgrade.
If multiple Windows clients attempt to log into an SMB session at the same time, one or more attempts might fail, and all clients will subsequently not see the share as being available.
Workaround: If you are using the SMB service on your Oracle Solaris system, do not upgrade to Oracle Solaris 11.4 until SRU 1 is available.
Removing one or more devices from a pool while the pool is under heavy I/O load can cause a deadlock in ZFS that prevents completion of I/O operations to that pool. The pool appears to be functional but the I/O operations are queued on the application side, up to the maximum size of the client queue.
The issue manifests itself in such a way that the device removal is making no progress. No data loss will occur due to this issue.
Workaround: Avoid removing devices from a pool when the pool is under load. If this issue occurs, you must reboot the system.
Disk manufacturers now provide larger capacity disks, also known as advanced format (AF) disks. An AF disk is a hard disk drive whose physical block size exceeds 512 bytes. AF disks use block sizes that are greater than 512 bytes, usually 4096 bytes, but their sizes can vary as follows:
4 KB native disk (4kn) – Uses a physical and logical block size of 4 KB
512-byte emulation (512e) – Uses a physical block size of 4 KB but reports a logical block size of 512 bytes
Review the following issues if you are considering the purchase of AF disks as new or replacement devices on your Oracle Solaris 11.4 system.
The failure of certain 512e disk drives to provide a power-safe feature can result in data loss if a power failure occurs during a read-modify-write (rmw) operation.
Workaround: Choose one of the following workarounds:
Confirm with the disk manufacturer that their 512e devices provide a power-safe feature.
No consistent power-safe identification appears on such drives, but they tend to be SATA drives. An indication that they are AF drives does not necessarily mean that they support 512 emulation (512e).
Do not use these drives on an Oracle Solaris system.
Installing and booting Oracle Solaris 11.4 on a 4kn disk on a SPARC system requires a volume table of contents (VTOC) label and PROM version 4.34.0.
Workaround: Choose one of the following workarounds:
If you want to install and boot Oracle Solaris 11.4 from a 4kn disk, then apply a VTOC label and confirm that your system is running this version.
For example:
# prtconf -pv | grep OBP version: 'OBP 4.34.0 ... '
Request a firmware upgrade from Oracle support.
For more information about using advanced format disks in Oracle Solaris 11.4, see Managing Devices in Oracle Solaris 11.4.