Hi All,
When we initially came up with specs of 'glusterd', we needed an option
to replace a dead brick, and few people even requested for having an
option to migrate the data from the brick, when we are replacing it.
The result of this is 'gluster volume replace-brick' CLI, and in the
relea
hi,
i have problem with x86_64 on server vs x86 on the client (both centos6)
i filled this bug
https://bugzilla.redhat.com/show_bug.cgi?id=862908
can you someone confirm that is real bug?
thanks
--
---
Marek Cervenka
===
Hello Gluster users
We had to migrate our gluster replicated store from three less capable nodes to
two more capable nodes. When we did that we seem to have some meta data
hanging around and at some point gluster crashed. All seemed to be fine for a
while.
Now we are trying to add in two mor
http://community.gluster.org/q/how-to-change-transport-type-on-active-volume---glusterfs-3-3/
On 10/11/12 4:41 PM, John Mark Walker wrote:
Cool - can you add this to http://community.gluster.org/ ?
-JM
- Original Message -
What I did was:
gluster volume stop VOLUME
gluster volume
Cool - can you add this to http://community.gluster.org/ ?
-JM
- Original Message -
> What I did was:
>
> gluster volume stop VOLUME
> gluster volume delete VOLUME
>
> On each peer on each brick I did:
> setfattr -x trusted.glusterfs.volume-id /mnt/brick1
> setfattr -x trusted.gfid /m
What I did was:
gluster volume stop VOLUME
gluster volume delete VOLUME
On each peer on each brick I did:
setfattr -x trusted.glusterfs.volume-id /mnt/brick1
setfattr -x trusted.gfid /mnt/brick1
setfattr -x trusted.glusterfs.volume-id /mnt/brick2
setfattr -x trusted.gfid /mnt/brick2
rm -r /mnt/b
Hi folks,
We found that samba performance downgrade a lot with glusterfs backend. volume
info as followed,
Volume Name: vol1
Type: Distribute
Status: Started
Number of Bricks: 1
Transport-type: tcp
Bricks:
Brick1: pana53:/data/
Options Reconfigured:
auth.allow: 192.168.*
features.quota: on
nfs.di
