From: Aleksey Senin <aleksey.senin@bladefusion.com>
To: unlisted-recipients:; (no To-header on input)
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: nfsroot 8k block size
Date: Mon, 09 May 2005 15:45:15 +0300 [thread overview]
Message-ID: <427F5B5B.1060800@bladefusion.com> (raw)
In-Reply-To: <1115642136.24625.11.camel@lade.trondhjem.org>
I'm looking on the output from 'mount' command and in /proc/mounts file
It shows that nfsroot mounted with 8k block size when I using nfsroot.
If client booted from disk it shows 32k.
I applied patches to the kernel on the server side, and it support 32k.
Trond Myklebust wrote:
> må den 09.05.2005 Klokka 08:33 (-0400) skreiv Trond Myklebust:
>
>>må den 09.05.2005 Klokka 14:53 (+0300) skreiv Aleksey Senin:
>>
>>>Yes. If I boot client from the disk with the same kernel, I can mount
>>>directory /bla/bla/bla with block size 32k, it meant the command
>>>mount -t nfs -o rsize=32768,wsize=32768 XXX:/bla/bla/bla /tmp/client
>>>work fine.
>>>I'm using kernel 2.4.25 on the server side, and kernel 2.4.30 on the
>>>client side.
>>
>>Only the 2.6 kernels support 32k by default.
>
>
> Note: this applies to the knfsd server only. The clients have supported
> 32k ever since 2.4.0.
>
> Cheers,
> Trond
>
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2005-05-09 12:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-09 11:13 nfsroot 8k block size Aleksey Senin
2005-05-09 11:43 ` Trond Myklebust
2005-05-09 11:53 ` Aleksey Senin
2005-05-09 12:33 ` Trond Myklebust
2005-05-09 12:35 ` Trond Myklebust
2005-05-09 12:45 ` Aleksey Senin [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=427F5B5B.1060800@bladefusion.com \
--to=aleksey.senin@bladefusion.com \
--cc=linux-fsdevel@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.