Casper.Dik at Sun.COM wrote: [cut] >> At earlier boot failures after a power outage, the behaviour was >> different, but the boot archive was recognized as inconsistent a handful >> of times. This bugs me. Otherwise, the machines run through without >> trouble, and with ZFS, the chances for a damaged boot archive should be >> zero. Here it approaches a two-digit percentage. > > That's actually not true: the boot-archive becomes inconsistent when, e.g., > wintertime/summertime commences, a USB device is connected/removed. > (or any other removable device ) > > That's why I typically use the commands listed above; that's because *I* > prefer the system to boot even when the boot-archive is out-of-date.
... and/or a frequent cron job that runs 'bootadm update-archive'; that command only actually reconstructs the archive if it is out of date, so most wakeups are free but one after a USB device plug etc will resync the archive ready for the next power failure. It may be possible to write a daemon that uses the new(ish) file events callbacks to monitor the set of files in the boot archive and reconstruct whenever something changes. Might make a nice mini project. Gavin
