jayl-news@accelerant.net (Jay Lessert) wrote in message news:<7109f92b.0401291245.2bdc0d96@posting.google. com>...
> ultrasparc3@hotmail.com wrote in message news:<2004028.204651.3924@cable.prodigy.com>...
> > are you aware that the boot code only understands plain (non-logging)
> > UFS? if any files necessary early in the boot process have their metadata
> > in the log then you will have problems.
>
> You mean if I yank the power plug right after installing a kernel
> jumbo patch? But I'm probably due for problems in that case,
> logging or not.

Typically, I've run into it if a kernel panic (for me, mostly from
reboot -d) occurred right after adding a driver, or too quickly after
a reconfiguration boot. Typically, either /etc/path_to_inst or
/etc/name_to_major has inconsistent metadata, causing the kernel to
become quite confused, and keeping boot from completing.

This happens much more often for kernel developers than it does for
most customers, but the subtlety of the errors which can occur means
that the current plan is to only turn on logging by default when
ufsboot supports using it.

- jonathan