Re: [Gluster-devel] xattrs and bug 9

[Jamson Hariss]

On Fri, 2009-08-14 at 14:33 -0400, Mark Mielke wrote:
> On 08/14/2009 02:26 PM, Gordan Bobic wrote:
> > 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?
> >
> > Maybe I'm missing something important here, but with AFR a file should 
> > reside on ALL bricks. If it isn't then something has gone badly wrong.
> 
> I think he means "which brick is authoritative". Or, that's what I 
> assumed anyways...
> 
> I suspect the purpose is for manual heal in the case that self-heal does 
> not work?
> 
> Cheers,
> mark
> 

Sorry, I must have mislead you. 

My configuration is distribute over replicate. Like so (client config):

volume replicate1
        type cluster/replicate
        subvolumes g1b1 g2b1
end-volume

volume replicate2
        type cluster/replicate
        subvolumes g1b2 g2b2
end-volume

volume distribute
  type cluster/distribute
  subvolumes replicate1 replicate2 
end-volume

And the question is - how to know on which replicate volume resides each
file from distribute?

JH