On Sun, Aug 25, 2013 at 11:23 PM, Vijay Bellur <vbellur@xxxxxxxxxx> wrote:
File size as reported on the mount point and the bricks can vary because of this code snippet in iatt_from_stat():
{
uint64_t maxblocks;
maxblocks = (iatt->ia_size + 511) / 512;
if (iatt->ia_blocks > maxblocks)
iatt->ia_blocks = maxblocks;
}
This snippet was brought in to improve accounting behaviour for quota that would fail with disk file systems that perform speculative pre-allocation.
If this aides only specific use cases, I think we should make the behaviour configurable.
Thoughts?
-Vijay
This is very unlikely the problem. st_blocks field values do not influence md5sum behavior in any way. The file size (st_size) would, but both du -k and the above code snipped only deal with st_blocks.
Bobby, it would help if you can identify the mismatching file and inspect and see what is the difference between the two files?
Avati
*Bobby Jacob*
-------- Original Message --------
Subject: [Gluster-users] FileSize changing in GlusterNodes
Date: Wed, 21 Aug 2013 05:35:40 +0000
From: Bobby Jacob <bobby.jacob@xxxxxxxxxxx>
To: gluster-users@xxxxxxxxxxx <gluster-users@xxxxxxxxxxx>
Hi,
When I upload files into the gluster volume, it replicates all the files
to both gluster nodes. But the file size slightly varies by (4-10KB),
which changes the md5sum of the file.
Command to check file size : du –k *. I’m using glusterFS 3.3.1 with
Centos 6.4
This is creating inconsistency between the files on both the bricks. ?
What is the reason for this changed file size and how can it be avoided. ?
Thanks & Regards,
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://supercolony.gluster.org/mailman/listinfo/gluster-users
