<div dir="ltr">From man (2) stat:<div><br></div><div><pre style="color:rgb(0,0,0)"> blksize_t st_blksize; /* blocksize for file system I/O */
blkcnt_t st_blocks; /* number of 512B blocks allocated */</pre></div><div class="gmail_extra"><br></div><div class="gmail_extra">The 128K you are seeing is "st_blksize" which is the recommended I/O transfer size. The number of consumed blocks is always reported as 512 byte blocks. The actual block size with which storage allocation happens depends on the backend filesystem.</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">Avati<br><br><div class="gmail_quote">On Mon, Nov 25, 2013 at 7:18 AM, Maik Kulbe <span dir="ltr"><<a href="mailto:info@linux-web-development.de" target="_blank">info@linux-web-development.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
I've come to notice that the file system block size reported from stat on a client is 128k, which is pretty high for the small files I use. On the other hand, I tested copying smaller files to the volume and it seems those 128k are not the real block size - when I copy two 64k files to the volume `df` reports only a change after both files have been copied.<br>
<br>
So my question would be what is the real block size for the Gluster volume? The block size of the underlying xfs? Or something else? And is it possible to read the real block size? We wanted to use the block size reported by stat to calculate the real file size use on disk but it seems that is not possible with Gluster..<br>
<br>
Thank you in advance,<br>
Maik<br>
______________________________<u></u>_________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a><br>
<a href="http://supercolony.gluster.org/mailman/listinfo/gluster-users" target="_blank">http://supercolony.gluster.<u></u>org/mailman/listinfo/gluster-<u></u>users</a><br>
</blockquote></div><br></div></div>