I should have also said that my volume is working well now and all is well.<div><br></div><div>-Jon</div><div><br><br><div class="gmail_quote">On Fri, Nov 2, 2012 at 1:21 PM, Jonathan Lefman <span dir="ltr"><<a href="mailto:jonathan.lefman@essess.com" target="_blank">jonathan.lefman@essess.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p>Thank you Brian. I'm happy to hear that this behavior is not typical. I am now using xfs on all of my drives. I also wiped out the entire /etc/glusterd directory for good measure. I bet that there was residual information from a previous attempt at a gluster volume that must have caused problems. Or moving to xfs from ext4 is an amazing fix, but I think this is less likely. </p>
<p>I appreciate your time responding to me.</p>
<p>-Jon</p><div class="HOEnZb"><div class="h5">
<div class="gmail_quote">On Nov 2, 2012 4:44 AM, "Brian Candler" <<a href="mailto:B.Candler@pobox.com" target="_blank">B.Candler@pobox.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Thu, Nov 01, 2012 at 08:03:21PM -0400, Jonathan Lefman wrote:<br>
> Soon after loading up about 100 MB of small files (about 300kb each),<br>
> the drive usage is at 1.1T.<br>
<br>
That is very odd. What do you get if you run du and df on the individual<br>
bricks themselves? 100MB is only ~330 files of 300KB each.<br>
<br>
Did you specify any special options to mkfs.ext4? Maybe -l 512 would help,<br>
as the xattrs are more likely to sit within the indoes themselves.<br>
<br>
If you start everything from scratch, it would be interesting to see df<br>
stats when the filesystem is empty. It may be that a huge amount of space<br>
has been allocated to inodes. If you expect most of your files >16KB then<br>
you could add -i 16384 to mkfs.ext4 to reduce the space reserved for inodes.<br>
But using xfs would be better, as it doesn't reserve any space for inodes,<br>
it allocates it dynamically.<br>
<br>
Ignore the comment that glusterfs is "not designed for handling large count<br>
small files" - 300KB is not small.<br>
<br>
Regards,<br>
<br>
Brian.<br>
</blockquote></div>
</div></div></blockquote></div><br></div>