On 08/21/2014 12:21 PM, Dinu Cosmin wrote:
> Hi,
>
> My setup consist in a s3ql mount exported by nfs. The max-object-size
> value used in mkfs.sql3 was 128 MB
>
> On the nfs client, the /proc/mount shows rsize=524288,wsize=524288
> meaning the nfs read and write block sizes are 512K.
>
>
> Now when I copy a file over the network to the nfs mount, the
> .s3ql/mount.log on the nfs server shows block size of 4K
>
> 2014-08-21 12:52:15.519 [pid=19104, thread='Dummy-23', module='s3ql.fs',
> fn='write', line=1037]: write(4, 10452992, datalen=*4096*): start
[..]
> My question is why the write block size is so small e.g. 4K? How can I
> increase the existing 4096 block size used in write?
This might well the "default" block size that is used by NFS for all
internal requests (i.e., requests that do not go over the network but to
the local file system).
I'm not an NFS expert though.
Best,
-Nikolaus
--
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«
--
You received this message because you are subscribed to the Google Groups
"s3ql" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
