<div dir="ltr">Justin,<div><br></div><div>Thanks for the response. That is exactly what I needed. See I had deleted the files but did not know which entries in .glusterfs to delete. The trick is the link count = 1 and not linked to another file | grep -v ' -> ' that gave me the complete list. There turned out to be 1k+ files and over 30T of hidden storage. </div>
</div><div class="gmail_extra"><br clear="all"><div><div><br></div><div>Bruce</div><div>Joink LLC</div><div>812-231-7078</div></div>
<br><br><div class="gmail_quote">On Fri, Mar 28, 2014 at 3:05 PM, Justin Dossey <span dir="ltr"><<a href="mailto:jbd@podomatic.com" target="_blank">jbd@podomatic.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Since the files in .glusterfs are hard links, your data isn't actually gone-- you could restore the lost data in fact if you were able to determine the names of the files that were deleted based on the contents of the hard links in the .glusterfs directory. Big "if" but we're talking about recovering data, so it's up to you. If practicable, it's smart to keep a list of inode-filepath associations somewhere, but this probably doesn't help now.<div>
<br></div><div>You can use find(1) to locate which of the .glusterfs files references one of the deleted files on the brick:</div><div>find /path/to/.glusterfs -links 1 -ls</div><div><br></div></div><div class="gmail_extra">
<br><br><div class="gmail_quote"><div><div class="h5">On Thu, Mar 27, 2014 at 1:29 PM, Bruce Spidel <span dir="ltr"><<a href="mailto:bruce.spidel@joinkllc.com" target="_blank">bruce.spidel@joinkllc.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5">
<div dir="ltr">In a moment of insanity I deleted a few hundred files in a gluster brick (30TB of 133TB) which is part of a distribute volume. I want these files deleted. but did not do it through the client. The volume is reporting a size as if they are still there. The files in .glusterfs are still there and I don't know which ones to delete.<div>
<br></div><div>I think the data was linked from the primary directories and the .glusterfs directories and when I deleted the files from the primary directories the data did not delete because of the links in .glusterfs.</div>
<div><br></div><div>Is it survivable to delete all of .glusterfs in one or all bricks and hope that gluster will repair it?</div><div><br clear="all"><div><div><br></div><div>Bruce</div><div>Joink LLC</div><div><a href="tel:812-231-7078" value="+18122317078" target="_blank">812-231-7078</a></div>
</div>
</div></div>
<br></div></div>_______________________________________________<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.org/mailman/listinfo/gluster-users</a><span class="HOEnZb"><font color="#888888"><br></font></span></blockquote>
</div><span class="HOEnZb"><font color="#888888"><br><br clear="all"><div><br></div>-- <br>Justin Dossey<br>
CTO, PodOmatic<div><br></div>
</font></span></div>
</blockquote></div><br></div>