Working with Firmware Upgrades
Same as "passthrough", except that the owner, group, and everyone ACL entries inherit the
execute permission only if the file creation mode also requests the execute bit.
The "passthrough" mode is typically used to cause all "data" files to be created with an identical
mode in a directory tree. An administrator sets up ACL inheritance so that all files are created
with a mode, such as 0664 or 0666. This all works as expected for data files, but you might
want to optionally include the execute bit from the file creation mode into the inherited ACL.
One example is an output file that is generated from tools, such as "cc" or "gcc". If the inherited
ACL does not include the execute bit, then the output executable from the compiler is not
executable until you use chmod(1) to change the permissions for the file.
To use this new mode, the storage pool must be upgraded. If you choose not to upgrade the pool
and attempt to use this new property, you will get an error indicating that the storage pool needs
to be upgraded first. There is no other implication of applying this update, and it can be ignored
if there is no need to use this new setting. Applying this update is equivalent to upgrading the
on-disk ZFS pool to ZFS Pool Version Summary.
Working with Firmware Upgrades
Following the application of a software upgrade, any hardware for which the upgrade includes
newer versions of firmware is upgraded. There are several types of devices for which firmware
upgrades may be made available; each has distinct characteristics.
Disks, storage enclosures, and certain internal SAS devices are upgraded in the background.
When this is occurring, the firmware upgrade progress is displayed in the left panel of the
Maintenance > System BUI view, or in the maintenance system updates CLI context. These
firmware upgrades are almost always hardware related, though it may briefly show some
number of outstanding updates when applying certain deferred updates to components other
than hardware.
As of 2010Q3.4, when there are outstanding updates, an informational or warning icon appears
next to the number of updates remaining. Clicking the icon brings up the Firmware Updates
dialog, which lists the current remaining updates. For each update we also show the current
version of the component, the time of the last attempted update, as well as the reason why the
last attempt did not succeed.
We consider any outstanding updates to be in one of 3 states: Pending, In Progress and Failed.
An update begins in the Pending state, and is periodically retried, at which time it moves into
the In Progress state. If we fail to upgrade, due to a transient condition, the upgrade is moved
back to the Pending state, and otherwise to the Failed state.
In general, it is only an indication of a problem if:
Maintaining the System 307
To Next Page
Loading...
Need help?
General