From: "Amir Hermelin" <amir@montilio.com>
To: "'Lever, Charles'" <Charles.Lever@netapp.com>
Cc: <nfs@lists.sourceforge.net>
Subject: RE: remounting with a different blocksize
Date: Thu, 18 Sep 2003 09:19:27 +0200 [thread overview]
Message-ID: <00d101c37db5$324ebf40$1301a8c0@CARTMAN> (raw)
In-Reply-To: <482A3FA0050D21419C269D13989C6113D06CAA@lavender-fe.eng.netapp.com>
I'm really only running a small and specific number of tests, one READ =
at a
time, files ranging from 8K to 256MB. Is there any place I can read =
about
the reasons why my client (Linux 2.4) isn't using the blocksize I need?
Thanks,
Amir.
-----Original Message-----
From: nfs-admin@lists.sourceforge.net
[mailto:nfs-admin@lists.sourceforge.net] On Behalf Of Lever, Charles
Sent: =E3 17 =F1=F4=E8=EE=E1=F8 2003 17:21
To: Amir Hermelin
Cc: nfs@lists.sourceforge.net
Subject: RE: [NFS] remounting with a different blocksize
hi amir-
using "rsize=3D8192" means the client *can* use 8KB reads,
it doesn't mean that it *always* will. there are a variety
of reasons the client might choose 4KB reads even though
it could send larger ones.
can you describe your workload?
> -----Original Message-----
> From: Amir Hermelin [mailto:amir@montilio.com]
> Sent: Wednesday, September 17, 2003 2:45 AM
> To: nfs@lists.sourceforge.net
> Subject: [NFS] remounting with a different blocksize
>=20
>=20
> Hi,
> I'm using RH Linux 2.4.20 on both machines. When I first
> mount one of the
> machines with a 4k read/write blocksize, the READ requests=20
> are 4K bytes.
> However, when I umount and then mount again with read/write=20
> blocksize of 8K,
> the READ requests are still 4K bytes.
>=20
> Any ideas on how I can properly change the blocksizes?
>=20
> Thanks,
> Amir.
>=20
>=20
>=20
>=20
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf=20
> _______________________________________________
> NFS maillist - NFS@lists.sourceforge.net=20
> https://lists.sourceforge.net/lists/listinfo/nfs
>=20
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf _______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-09-18 6:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-17 15:20 remounting with a different blocksize Lever, Charles
2003-09-18 7:19 ` Amir Hermelin [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-09-17 6:45 Amir Hermelin
2003-09-17 10:57 ` Steve Dickson
2003-09-17 14:04 ` Amir Hermelin
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='00d101c37db5$324ebf40$1301a8c0@CARTMAN' \
--to=amir@montilio.com \
--cc=Charles.Lever@netapp.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.