Have upgraded my cluster to debian jessie, so able to natively test 3.7.5 I?ve noticed some peculiarities with reported file sizes on the gluster mount but I seem to recall this is a known issue with shards? Source file is sparse, nominal size 64GB, real size 25GB. However underlying storage is ZFS with lz4 compression which reduces it to 16GB No Shard: ls ?lh : 64 GB du ?h : 25 GB 4MB Shard: ls ?lh : 144 GB du ?h : 21 MB 512MB Shard: ls ?lh : 72 GB du ?h : 765 MB a du ?sh of the .shard directory show 16GB for all datastores Is this a known bug for sharding? Will it be repaired eventually? Sent from Mail for Windows 10 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20151101/e631d802/attachment.html>
More concerningly, the files copied to the gluster shard datastores have a difference md5sum to the original. Thats a fatal flaw. Sent from Mail for Windows 10 From: Lindsay Mathieson Sent: Sunday, 1 November 2015 10:59 AM To: gluster-users Subject: Shard file size (gluster 3.7.5) Have upgraded my cluster to debian jessie, so able to natively test 3.7.5 I?ve noticed some peculiarities with reported file sizes on the gluster mount but I seem to recall this is a known issue with shards? Source file is sparse, nominal size 64GB, real size 25GB. However underlying storage is ZFS with lz4 compression which reduces it to 16GB No Shard: ls ?lh???? : 64 GB du ?h ???? : 25 GB 4MB Shard: ls ?lh???? : 144 GB du ?h ???? : 21 MB 512MB Shard: ls ?lh???? : 72 GB du ?h ???? : 765 MB a du ?sh of the .shard directory show 16GB for all datastores Is this a known bug for sharding? Will it be repaired eventually? Sent from Mail for Windows 10 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20151101/d267c364/attachment.html>
Could you share (1) the output of 'getfattr -d -m . -e hex <path>' where <path> represents the path to the original file from the brick where it resides (2) the size of the file as seen from the mount point around the time when (1) is taken (3) output of 'gluster volume info' -Krutika ----- Original Message -----> From: "Lindsay Mathieson" <lindsay.mathieson at gmail.com> > To: "gluster-users" <gluster-users at gluster.org> > Sent: Sunday, November 1, 2015 6:29:44 AM > Subject: [Gluster-users] Shard file size (gluster 3.7.5)> Have upgraded my cluster to debian jessie, so able to natively test 3.7.5> I?ve noticed some peculiarities with reported file sizes on the gluster mount > but I seem to recall this is a known issue with shards?> Source file is sparse, nominal size 64GB, real size 25GB. However underlying > storage is ZFS with lz4 compression which reduces it to 16GB> No Shard:> ls ?lh : 64 GB> du ?h : 25 GB> 4MB Shard:> ls ?lh : 144 GB> du ?h : 21 MB> 512MB Shard:> ls ?lh : 72 GB> du ?h : 765 MB> a du ?sh of the .shard directory show 16GB for all datastores> Is this a known bug for sharding? Will it be repaired eventually?> Sent from Mail for Windows 10> _______________________________________________ > Gluster-users mailing list > Gluster-users at gluster.org > http://www.gluster.org/mailman/listinfo/gluster-users-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20151102/49d51dd9/attachment.html>