From: Jens Axboe <axboe@suse.de>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: RPC request reserved 0 but used 96
Date: Sat, 15 May 2004 10:38:33 +0200 [thread overview]
Message-ID: <20040515083831.GR17326@suse.de> (raw)
Hi,
Seeing lots of these on a small server that hosts nfs shares (root and
"normal").
router:~ # dmesg | tail -n5
RPC request reserved 0 but used 96
RPC request reserved 0 but used 96
RPC request reserved 0 but used 140
RPC request reserved 0 but used 140
RPC request reserved 0 but used 96
I see nfs stalls on the client, doesn't seem to be directly related to
when the above messages happen.
--
Jens Axboe
next reply other threads:[~2004-05-15 8:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-15 8:38 Jens Axboe [this message]
2004-05-15 8:58 ` RPC request reserved 0 but used 96 Jens Axboe
2004-05-15 10:36 ` Jens Axboe
[not found] ` <20040518040613.GB10633@fieldses.org>
2004-05-18 11:03 ` Jens Axboe
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=20040515083831.GR17326@suse.de \
--to=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.