<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=EN-AU link=blue vlink="#954F72"><div class=WordSection1><p class=MsoNormal>Have upgraded my cluster to debian jessie, so able to natively test 3.7.5</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>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?</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Source file is sparse, nominal size 64GB, real size 25GB. However underlying storage is ZFS with lz4 compression which reduces it to 16GB</p><p class=MsoNormal><span style='font-family:"Courier New"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Courier New"'>No Shard:<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Courier New"'>ls –lh : 64 GB<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Courier New"'>du –h : 25 GB<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Courier New"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Courier New"'>4MB Shard:<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Courier New"'>ls –lh : 144 GB<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Courier New"'>du –h : 21 MB<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Courier New"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Courier New"'>512MB Shard:<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Courier New"'>ls –lh : 72 GB<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Courier New"'>du –h : 765 MB<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Courier New"'><o:p> </o:p></span></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>a du –sh of the .shard directory show 16GB for all datastores<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Is this a known bug for sharding? Will it be repaired eventually?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Sent from <a href="http://go.microsoft.com/fwlink/?LinkId=550986">Mail</a> for Windows 10</p></div></body></html>