On Fri, 14 Aug 2009, Jamson Hariss wrote:
Hello.
In 2.0.6 "bug 9" has been "fixed", meaning that extended attributes
'trusted.afr.volume' are no longer visible from mount point. I was using
those attributes to determine on which brick files actually reside and
perform checksumming on them to ensure that replicate works as intended
(which it occasionally does not).
My question - is there a way in 2.0.6 to know on which brick file
actually resides in AFR? On a side note - why it was necessary to remove
those attributes in the first place?
I second that question.
Extended attributes are pretty much critical for Disco. It uses them to
decide where to execute tasks, to optimize data locality:
http://github.com/tuulos/disco/blob/c1d4ffadeba40af8a8547dd6afce562d267e464e/pydisco/disco/dfs/gluster.py#L36
If the extended attributes are really removed (I haven't upgraded yet to
2.0.6), what's the official way of finding out where files are physically
stored?
Ville
