If a drive dies and you want to repopulate its replacement with `ls -R /mnt/glusterfs` is it necessary to have the options set too, or is this specific to the scale-n-defrag.sh script? P On Thu, Jul 29, 2010 at 12:22 AM, Amar Tumballi <amar at gluster.com> wrote: > Hi Michael, > > Sorry for the confusion on 'scale-n-defrag.sh' script. > > To make sure the script does defrag, you need to have two options set in > distribute volume. > > 'option unhashed-sticky-bit on' > 'option lookup-unhashed on' > > Without these options it will not move the data files in backend. If you > don't want to bring down the current mount point to run the defrag, you can > have another mount point with changed volume file, and run defrag over it. > > Let us know if you have any more questions regarding defrag process. > > Regards, > Amar > > On Wed, Jul 28, 2010 at 9:37 PM, Moore, Michael > <Michael.Moore at lifetech.com>wrote: > >> Hi, >> >> ? I am trying to add several new backend volumes to an existing GlusterFS >> setup. ?I am running GlusterFS 3.0.4 using the distribute translator. ?I've >> tried running the "scale-n-defrag.sh" script to redistribute the data across >> the additional volumes, but after running for a significant time, nothing >> was significantly redistributed. ?What are the proper steps to do to >> redistribute the data? ?Do I need to clean up the links GlusterFS makes on >> the backends before I run scale-n-defrag? >> >> ? I am running GlusterFS 3.0.4 on top of CentOS 5.4. ?This is not running >> GlusterSP. >> > > _______________________________________________ > Gluster-users mailing list > Gluster-users at gluster.org > http://gluster.org/cgi-bin/mailman/listinfo/gluster-users > > -- http://philcryer.com
