<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
I've posted a couple of messages recently about a problem I'm having where<br>
some files in my cluster are not showing up under unify, despite existing<br>
properly on the individual storage bricks.<br>
</blockquote><div><br>This would happen under unify only if the namespace entry is missing for the file. Self heal of unify should ideally fix these cases. If for some reason (bug?) the self-heal is not fixing it, you could try manually 'touch' ing the file in the backend of namespace and see if you can access the file.<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
I've been trying to go through the source code and understand what's<br>
happening, and the only thing I've got at the moment is that somehow some of<br>
the metadata associated with the files isn't right. My understanding is<br>
limited but the only way I can see the problem I'm having happening is if<br>
the inode generation count on my files is somehow invalidly set.<br>
<br>
Is there some way I can manually reset it on the files on my bricks?<br>
</blockquote><div><br>inode generation number would generally not make a file disappear.<br><br>avati <br></div></div>