Filter
Top Products
7 System Administration, Management, and Monitoring
This chapter contains notes about system administration, management, and monitoring.
7.1 Perform A Dry Run Before Using The si_updateclient Utility To Update
Nodes
The si_updateclient utility can leave nodes in an unbootable state in certain situations. You
can still use si_updateclient to deploy image changes to nodes. However, before you update
any nodes, HP recommends that you perform a dry run first to ensure that files in the /boot
directory are not updated. Updating files in /boot can result in nodes being unable to boot.
You can retieve a list of files that will be updated by si_updateclient by specifying
--dry-run on the command line.
7.2 Possible Problem With ext3 File Systems On SAN Storage
Issues have been reported when an ext3 file system fills up to the point where ENOSPC is returned
to write requests for a long period of time, and the file system is subsequently unmounted. A
forced check is initiated (fsck -fy) before the next mount. It appears that the fsck checks
might corrupt the file system inode information.
This problem has been seen only on fibre channel (SAN) storage; it has not been seen with directly
attached storage or NFS storage.
For more information about details and work arounds, consult Bugzilla number 175877 at the
following URL:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=175877
7.1 Perform A Dry Run Before Using The si_updateclient Utility To Update Nodes 31