<div>Hi Jan,</div><div><br></div><div>This means, the 'trusted.gfid' xattr (which is very much required by the glusterfs to work fine and is sort of inode number of a file in regular fs) is missing for that particular folder. One way to fix it is by below steps</div>
<div><br></div><div>on other nodes where you don't have any logs:</div><div><br></div><div>sh# getfattr -d -m trusted.gfid <some folder></div><div><output></div><div><br></div><div>on the node which has issue of logs:</div>
<div><br></div><div>sh# setfattr -n trusted.gfid -v <value got in other node> <some folder></div><div><br></div><div>This should solve the issue.</div><div><br></div><div>This state is mostly reached by not having this one machine ready before having a client machine mounting the volume and accessing these folders.</div>
<div><br></div><div>Regards,</div><div>Amar</div><div><br><div class="gmail_quote">On Sat, May 21, 2011 at 4:23 AM, Jan Wynholds <span dir="ltr"><<a href="mailto:jwynholds@510systems.com">jwynholds@510systems.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Hello:<br>
<br>
We have a 8 node gluster setup here. Some of the nodes were running<br>
3.0.7 and 3.0.8. One of the nodes has an xfs filesystem (which is the<br>
only difference between the rest which are ext4).<br>
<br>
On the xfs (that was also previously running 3.0.7 and 8), grows logs<br>
at an alarming rate (gigs a day).<br>
<br>
The logs are filled with errors such as:<br>
<br>
[2011-05-20 15:10:46.630875] E [posix.c:438:posix_lookup]<br>
0-store1-posix: lstat on [some folder] failed: No data available<br>
<br>
After looking through the documentation, and traffic on the mailing<br>
lists, I have come up empty on an explanation.<br>
<br>
Any insight would be most appreciated.<br>
<br>
--cheers<br>
<br>
jan<br><br></blockquote></div></div>