From: Luther Huffman lutherh@infinet.com
Subject: Slave buffer problem
Date: Mon, 15 Jul 1996 00:09:19 +0100 [thread overview]
Message-ID: <19960714230919.zUjDdvfB2TGGHl1dwl8pSsl_P3tMsdbm736G0bDn_cg@z> (raw)
I have a little information on the problems I've been having of applications
mysteriously freezing up my system console and displaying the message "8
1/2: slave buffer: no free mount rpc buffer". There really does appear to be
a link between this problem and the error messages which a file system check
produces. Here's sample output from disk/kfs:
term% disk/kfs -f /dev/hd1fs
check: "/386/bin/aux/mapd": qid out of range 113bb
check: "/386/bin/fb/twb": qid out of range 115b8
check: "/386/bin/fb/bit2enc": qid out of range 115c7
check: "/386/bin/fb/enc2bit": qid out of range 115e4
check: "/386/bin/fb/ikon": qid out of range 115fb
check: "/386/bin/fb/mugs": qid out of range 11614
check: "/386/bin/fb/paint": qid out of range 1161b
check: "/386/bin/fb/scale": qid out of range 1163a
check: "/386/lib/perl/": qid out of range 12f8e
check: "/386/lib/perl/5.00301/": qid out of range 12f8f
check: "/386/lib/perl/5.00301/CORE/": qid out of range 12f91
check: "/386/lib/perl/5.00301/CORE/arpa/": qid out of range 12f92
check: "/386/lib/perl/5.00301/CORE/arpa/inet.h": qid out of range 12fae
check: "/386/lib/perl/5.00301/CORE/EXTERN.h": qid out of range 12f93
check: "/386/lib/perl/5.00301/CORE/INTERN.h": qid out of range 12f94
check: "/386/lib/perl/5.00301/CORE/XSUB.h": qid out of range 12f95
check: "/386/lib/perl/5.00301/CORE/av.h": qid out of range 12f96
check: "/386/lib/perl/5.00301/CORE/cop.h": qid out of range 12f97
check: "/386/lib/perl/5.00301/CORE/cv.h": qid out of range 12f98
6051 bad qids
term%
I've noticed, as an example, if a perl script of mine loads a module from
/386/lib/perl I get the failure. If the perl script loads a module from
/sys/lib/perl everything proceeds normally. Similar things appear to occur
for other programs doing some kind of access in these directories as well.
The normal file and directory commands (ls, cat, etc.) seem to work just
fine with these directories.
Does this give rise to any new ideas, anyone?
---
Luther Huffman lutherh@stratcom.com
Strategic Computer Solutions, Inc.
http://www.stratcom.com/
next reply other threads:[~1996-07-14 23:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-07-14 23:09 Luther [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:37 philw
1996-07-15 0:04 David
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=19960714230919.zUjDdvfB2TGGHl1dwl8pSsl_P3tMsdbm736G0bDn_cg@z \
--to=9fans@9fans.net \
/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).