From: 김경표 <kpkim@gluesys.com>
To: <nfs@lists.sourceforge.net>
Subject: The actimeo seems not work
Date: Mon, 2 May 2005 19:49:43 +0900 [thread overview]
Message-ID: <003001c54f04$a6fd2a80$6b00a8c0@hgichon> (raw)
[-- Attachment #1: Type: text/plain, Size: 3638 bytes --]
hello list.
I have some question how to work of linux nfs client cache.
I was proceeding two test.
One is solaris 9 client with linux server.
The other is linux client with linux server.
Linux server and client kernel version is 2.4.27.
nfs-util version is 1.0.4.
[ mount option list ]
Linux server export option is rw,async.
Linux client mount optione is just actimeo=0.
Another linux client mount option is actimeo=100.
Solaris9 mount option is soft,xattr,rw.
[ linux client setting ]
192.168.1.212:/vol1 /mnt1 nfs rw,v3,rsize=8192,wsize=8192,acregmin=0,acregmax=0,acdirmin=0,acdirmax=0,hard,udp,lock,addr=192.168.1.212 0 0
192.168.1.212:/vol1 /mnt nfs rw,v3,rsize=8192,wsize=8192,acregmin=100,acregmax=100,acdirmin=100,acdirmax=100,hard,udp,lock,addr=192.168.1.212 0 0
[ Solaris 9 test ]
2 solaris 9 clients ----> linux server.
After i touch a file on one solaris client, I type ls -al the file on the other solaris client.
And i found that the file attribute(mtime) was updated randomly.(0 sec ~ 30sec)
The solais9 client is my customer machine.
My client want that the file attribute update interval is to 0 sec.
So I recommand to check nfs mount option in solaris 9 ( actimeo, acregXXX...).
[ linux client test ]
Test procedure is same with solaris9.
But, resut is not same.
Linux client shows up-to-dated file attribute.
As I know, linux nfs client default mount option is acregmin is 3.
So i change the mount option to actimeo=100.
But result is not different.
So I wonder that actimeo option is a available.
i tried tcpdump.
when mount option is actimeo=0 ( in linux client)
linux-client> ls -al /mnt/test.test
linux-client>-rwxrwxrwx 1 root root 12 Apr 29 16:59 /mnt/test.test
linux-server tcpdump output
-----------------------------------------------------------
18:51:52.561558 GRVC-C.4105878944 > 192.168.1.212.nfs: 120 access [|nfs] (DF)
18:51:52.561588 192.168.1.212.nfs > GRVC-C.4105878944: reply ok 120 access c 0000 (DF)
18:51:52.561683 GRVC-C.4122656160 > 192.168.1.212.nfs: 132 getattr [|nfs] (DF)
18:51:52.561759 192.168.1.212.nfs > GRVC-C.4122656160: reply ok 112 getattr REG 100777 ids 0/0 [|nfs] (DF)
-------------------------------------------------------------
when mount option is actimeo=100 ( in linux client)
linux-client> ls -al /mnt1/test.test
linux-client>-rwxrwxrwx 1 root root 12 Apr 29 16:59 /mnt/test.test
linux-server tcpdump output
-------------------------------------------------------------
18:55:37.860627 GRVC-C.4189765024 > 192.168.1.212.nfs: 120 access [|nfs] (DF)
18:55:37.860694 192.168.1.212.nfs > GRVC-C.4189765024: reply ok 120 access c 0000 (DF)
18:55:37.860874 GRVC-C.4206542240 > 192.168.1.212.nfs: 116 getattr [|nfs] (DF)
18:55:37.860932 192.168.1.212.nfs > GRVC-C.4206542240: reply ok 112 getattr DIR 40777 ids 99/99 [|nfs] (DF)
18:55:37.861123 GRVC-C.4223319456 > 192.168.1.212.nfs: 132 getattr [|nfs] (DF)
18:55:37.861147 192.168.1.212.nfs > GRVC-C.4223319456: reply ok 112 getattr REG 100777 ids 0/0 [|nfs] (DF)
18:55:37.861373 GRVC-C.4240096672 > 192.168.1.212.nfs: 132 getattr [|nfs] (DF)
18:55:37.861387 192.168.1.212.nfs > GRVC-C.4240096672: reply ok 112 getattr REG 100777 ids 0/0 [|nfs] (DF)
-------------------------------------------------------------
As you see, two more getattr appeared in actimeo=100.
linux nfs client code seems different by actimeo option.
but I can't verify the affect of nfs client cache . ( aspect of file attribute cacheing)
anybody help me?
How can i verify the affect of nfs client cache.
sorry poor my english.
[-- Attachment #2: Type: text/html, Size: 6576 bytes --]
next reply other threads:[~2005-05-02 10:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-02 10:49 김경표 [this message]
2005-05-02 12:37 ` The actimeo seems not work Neil Horman
2005-05-02 13:02 ` Trond Myklebust
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='003001c54f04$a6fd2a80$6b00a8c0@hgichon' \
--to=kpkim@gluesys.com \
--cc=nfs@lists.sourceforge.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 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.