Should this command be run on the servers or the clients? I have done both, and
still have issues.
And also is it correct as listed below? I get "no such attribute" errors.
[r...@g1 ~]# find /export/g1a -type d -exec setfattr -x trusted.glusterfs.dht
{} \;
setfattr: /export/g1a/data: No such attribute
setfattr: /export/g1a/data/prj: No such attribute
setfattr: /export/g1a/data/prj/N89: No such attribute
setfattr: /export/g1a/data/prj/N89/DATA2-STFF: No such attribute
setfattr: /export/g1a/data/prj/N89/DATA2-STFF/DATA: No such attribute
.......
Thanks,
Thomas
On Nov 19, 2009, at 12:12 PM, Amar Tumballi wrote:
>> What's the best way to add bricks, and get distribute to use them? I
>> added 2 more bricks, and the total size increased for the filesystem,
>> but i can't get any traffic on the new disks. I remounted the
>> filesystem, and ran an ls -Rl , but i still don't see any traffic to
>> the disks. I do see that the file tree was created on the new disks.
>
> Currently there is no 'hot' add feature which will take care of the
> addition of new bricks. To achieve the proper distribution, you need
> to force 'distribute' self heal by removing the extended attribute on
> the directories.
>
> Try running this:
>
> bash# find /mnt/glusterfs -type d -exec setfattr -x trusted.glusterfs.dht {}
> \;
>
> (Note that this works for versions 2.0.8 or higher).
>
> Regards,
_______________________________________________
Gluster-users mailing list
[email protected]
http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
