From: philw@plan9.bell-labs.com philw@plan9.bell-labs.com
Subject: Slave buffer problem
Date: Sun, 14 Jul 1996 20:37:27 -0400 [thread overview]
Message-ID: <19960715003727.PJ6z_ebtWcLsocX7kS14DeT-joVTqCt03WmsDfSsJyY@z> (raw)
qid out of range seems to happen because an
array (qbits in disk/kfs/chk.c) is too small -
it does not necessarily mean the file system
is bad. Try changing line 91 of chk.c to
sizqbits = ((1<<18) + 7) / 8; /* botch */
phil.
next reply other threads:[~1996-07-15 0:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-07-15 0:37 philw [this message]
-- strict thread matches above, loose matches on Subject: below --
1996-07-16 12:58 forsyth
1996-07-15 14:27 philw
1996-07-15 9:18 Boyd
1996-07-15 1:41 Luther
1996-07-15 0:04 David
1996-07-14 23:09 Luther
1996-07-12 17:08 Luther
1996-07-12 16:33 Scott
1996-07-12 4:32 Luther
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19960715003727.PJ6z_ebtWcLsocX7kS14DeT-joVTqCt03WmsDfSsJyY@z \
--to=philw@plan9.bell-labs.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).