From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Mon, 15 Jul 1996 02:41:01 +0100
From: Luther Huffman lutherh@infinet.com
Subject: Slave buffer problem
Topicbox-Message-UUID: 48ef1b72-eac8-11e9-9e20-41e7f4b1d025
Message-ID: <19960715014101.38T1DfBVcPCM39e8oQqcp6ICfNMY_tTmQ8qoBLrpH9U@z>

At 08:37 PM 7/14/96 -0400, you wrote:
>is bad. Try changing line 91 of chk.c to
>
>	sizqbits = ((1<<18) + 7) / 8;		/* botch */
>

Thanks, Phil! That does indeed stop disk/kfs from reporting bad qids. I
still get the messages during system startup after an OS failure, but I
believe that's caused by the fact fs check is called at that point. I
imagine there is a magic variable similar to sizqbits in fs.
     The whole thing does make me believe that any link between the bad qid
message and the slave buffer failure is at best indirect. There may,
however, be another system constant that I exceeded the same time as the qid
variable.
     Does anyone know from where the "8 1/2: slave buffer: no free mount rpc
buffer" message originates? I've grepped up the usual suspects, but haven't
found the message's source yet. And I don't have enough system resources to
do a global grep/awk.
---
Luther Huffman		lutherh@stratcom.com
Strategic Computer Solutions, Inc.
http://www.stratcom.com/