From: 宫勐 <shadowinlife@gmail.com>
To: Bian Naimeng <biannm@cn.fujitsu.com>
Cc: linux-nfs <linux-nfs@vger.kernel.org>
Subject: Re: pNFS: trouble test with fscache
Date: Wed, 15 Sep 2010 17:39:32 +0800 [thread overview]
Message-ID: <AANLkTimVTFNo3i2td=tcORTg0-yaLhM0dEXsXhku5khR@mail.gmail.com> (raw)
In-Reply-To: <4C9091A7.7030502@cn.fujitsu.com>
Thank you
I have checked the memory ( 12G.) and sometimes memory is only 512M
(I set it in grub.conf)
fscache works well I have sent /proc/fs/fscache/states to David
(RedHat who write fscache)
ENOBUFS is just normal infor
But once fscache detect a ENOBUFS It can't alloc more buff Then
no more data can be write to disk
nfs_readpages_to_fscache __nfs_readpages_from_fscache may report ENOBUF
After that no buff will be alloc
Thank you for replaying this mail
yours
GongMeng
On Wed, Sep 15, 2010 at 5:28 PM, Bian Naimeng <biannm@cn.fujitsu.com> wrote:
>> S:
>>
>> I want to get benchmark from pNFS+ fscache with iozone
>>
>> But iozone can't work well
>> /proc/fs/nfsfs/volumes show that the fsc is YES
>>
>> I have open cachefiled and mount a ssd (ext3/user_xattr) on /var/fscache
>>
>> When I use iozone to test read/re-read it can't write page to the SSD DISK
>>
>> /var/log/messages show that first it can write 4 pages successfully
>>
>> after NFS: nfs_getpages_from_fscache: no page: -105
>
> Please confirm whether do you have enough memory when get this error,
> i guess iozone eats lot of memory.
>
> And, maybe the information of /proc/fs/fscache/states is useful, please
> puts it.
>
> --
> Regards
> Bian Naimeng
>
>
prev parent reply other threads:[~2010-09-15 9:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-15 7:48 pNFS: trouble test with fscache 宫勐
2010-09-15 9:28 ` Bian Naimeng
2010-09-15 9:39 ` 宫勐 [this message]
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='AANLkTimVTFNo3i2td=tcORTg0-yaLhM0dEXsXhku5khR@mail.gmail.com' \
--to=shadowinlife@gmail.com \
--cc=biannm@cn.fujitsu.com \
--cc=linux-nfs@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 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).