Thanks, Thomas, for your reply. My response is inline. On 08/22/2016 04:11 AM, LEIBOVICI Thomas wrote: > > On 08/19/16 19:35, Jessica Otey wrote: >> >> PathCheck | Failed to get parent+name for [0x93ca92:0x709d8371:0x0]: >> No data available > > Hi Jessica, > > The error you see occurs when getxattr of "trusted.link" returns ENODATA.
Our file system is mounted with the "user_xattr" option. Although it took FOREVER to do this readlog (a few times as long as the initial scan did), it did complete successfully. Can I assume, then, that these errors are not some sort of misconfiguration but rather they reflect changes in the filesystem? Perhaps it took so long because it was run so long after a file system scan? What I'm trying to understand better is the relationship between scanning a file system and using the changelogs feature. 1) If changelogs is in fact working, does that mean that I *never* need to do a file system scan again? Or is it still a good idea to do occasional, full-system scans? If so, at what interval? 2) With changelogs in the picture, is there a way to indicate how up-to-date the information issued by robinhood reports is? Does one just assume it is real-time at that point, and thus the date of last scan (as reported by rbh-report -a) becomes irrelevant as an indicator of data freshness? Thanks, Jessica > > To troubleshoot this you can: > - check this entry path: > lfs fid2path fsname 0x93ca92:0x709d8371:0x0 > - try to get this attribute from command line: > getfattr -n trusted.link <path_to_entry> > - verify that the filesystem is mounted with the "user_xattr" option. > > Regards, > Thomas -- Jessica Otey System Administrator II North American ALMA Science Center (NAASC) National Radio Astronomy Observatory (NRAO) Charlottesville, Virginia (USA) ------------------------------------------------------------------------------ _______________________________________________ robinhood-support mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/robinhood-support
