Thanks to several folks for quick responses. Oisin McGuinness pointed out,
to my chagrin, that there was a recent summary on this problem, which
said the following:
-------------------------------------------------------------------------------
-
The correct parameter to set is the msgbuf_size to 64K
>From the manual:
message-buffer-size msgbuf_size
The size of the message buffer that is used to store boot log messages.
Default value: 4096
Example:
generic:
msgbuf_size = 16384
message-buffer-size = 16384
in the sysconfigtab .
-------------------------------------------------------------------------------
-
The poster who had this problem had recently added a controller to the
kernel config, and said "This machine has a lot of scsi controllers and disks,
including an HSZ50." Ours doesn't really have that many controllers, and it
has been this way from the beginning, but it does have an HSZ70 attached.
I also heard from Chris Wilson, who actually had the problem and posted,
and he suggested the above settings, and to use "file" and "scu" to
find device info in the meantime:
file /dev/rrz0a
or
file /dev/rmt0h
What's curious is we have not tinkered with the msgbuf params on any of
our hosts, and some have the problem and some don't, and they really are
similarly configured. I'll change the settings and hope for the best.
Thanks for the quick responses!
--
Judith Reed
jreed_at_appliedtheory.com
(315) 453-2912 x335
Received on Mon Jun 28 1999 - 15:53:07 NZST