On Sun, Feb 5, 2012 at 10:34 PM, Brian Candler <B.Candler at pobox.com> wrote: > On Sun, Feb 05, 2012 at 05:30:40PM +0530, Anand Avati wrote: >> > Alternatively: is it possible to determine for each file which brick it >> > resides on? >> >> Yes, there is the virtual extended attribute >> "trusted.glusterfs.pathinfo" which gives you the location (hostname) >> of a file. > > # getfattr -n trusted.glusterfs.pathinfo /mnt/test-volume/Bonnie.6790/00001/0000000065GEmkQPntG > getfattr: Removing leading '/' from absolute path names > # file: mnt/test-volume/Bonnie.6790/00001/0000000065GEmkQPntG > trusted.glusterfs.pathinfo="(<DISTRIBUTE:test-volume-dht> <POSIX:storage1:/data/sdc/test/Bonnie.6790/00001/0000000065GEmkQPntG>)" > > Cool :-) > > Is there something comparable a client can do on the mountpoint to get a > list of the component bricks in a volume? You can do the getfattr on a directory (say the mount point directory) and get the list of all bricks. Avati
