From: Ed Swierk <eswierk@kealia.com>
To: nfs@lists.sourceforge.net
Subject: Determining version, current block size, setting default
Date: Wed, 19 Mar 2003 17:16:52 -0800 [thread overview]
Message-ID: <3E791684.4070403@kealia.com> (raw)
Hello,
I'm running Linux 2.4.18 kernels on my NFS server and clients, and am trying
to debug what seems to be an incorrectly configured block size.
Are there ways to:
- determine what version of the NFS protocol is being used by an existing
NFS mount?
- determine what block size is being used for an existing NFS mount?
- set the default block size on the NFS (v3?) server, so I don't have to
specify rsize and wsize on every client?
Any help would be appreciated.
--Ed
-------------------------------------------------------
This SF.net email is sponsored by: Does your code think in ink?
You could win a Tablet PC. Get a free Tablet PC hat just for playing.
What are you waiting for?
http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next reply other threads:[~2003-03-20 1:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-20 1:16 Ed Swierk [this message]
2003-03-20 9:47 ` Determining version, current block size, setting default 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=3E791684.4070403@kealia.com \
--to=eswierk@kealia.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.