Re: oops pauser. / boot_delayer

[David Lang <dlang@digitalinsight.com>]

On Sat, 7 Jan 2006, Arjan van de Ven wrote:

> On Sat, 2006-01-07 at 13:44 -0800, Kurtis D. Rader wrote:
> > On Thu, 2006-01-05 06:11:05, Dave Jones wrote:
> > > On Thu, Jan 05, 2006 at 08:30:16AM +0100, Bernd Eckenfels wrote:
> > > > Randy.Dunlap <rdunlap@xenotime.net> wrote:
> > > >> This one delays each printk() during boot by a variable time
> > > >> (from kernel command line), while system_state == SYSTEM_BOOTING.
> > > >
> > > > This sounds a bit like a aprils fool joke, what it is meant to do? You can
> > > > read the messages in the bootlog and use the scrollback keys, no?
> > >
> > > could be handy for those 'I see a few messages that scroll, and the
> > > box instantly reboots' bugs.  Quite rare, but they do happen.
> >
> > Another very common situation is a system which fails to boot due to
> > failures to find the root filesystem. This can happen because of device name
> > slippage, root disk not being found, the proper HBA driver isn't present in
>
> mount by label fixes some of that but not all

there appears to be a limit on how many disks get checked for their label. 
I've got one system where I've got 2xraid cards each with 8 drives on them 
and then another raid card with my boot disk on it.

depending on how I have the two raid cards the boot disk can be anything 
from sdc to sdq, mounting by label works for sdc, but not for sdq.

David Lang

--
There are two ways of constructing a software design. One way is to make it so simple that there are obviously no deficiencies. And the other way is to make it so complicated that there are no obvious deficiencies.
 -- C.A.R. Hoare

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/