Chetan Ahuja wrote:
I posted this on irc (#gluster) a couple of times in the last few days but
got no response. Trying my luck here:
chetan I'm seeing this crash in 2.0.1 server codebase
#4 0x7f6a42848a56 in free () from /lib/libc.so.6
#5 0x7f6a4157ff99 in __socket_ioq_new
Hi,
I am faced with an issue of following type:
Primary Vol1 acting as client and server with mount point
/mnt/glusterfs and with data dir as /home/data
Secondary Vol2 acting as server with data dir as /home/data
Have created a symlink data under /mnt/ pointing to glusterfs on vol1
Hi ,
Its my seconds post regarding that , its stange
nobody noticed that if 1 node in replication pair reboots or something
the replication is no longer good and not in sync ?
What i mean is :
- Files got updated on the other server does not replicate back to the
other node
while was offline say
Hi
If i'm not wrong it will be synced once you try to access any
of the unsynced files, except if the file does not exist on the
first volume
Hi ,
Its my seconds post regarding that , its stange
nobody noticed that if 1 node in replication pair reboots or something
the replication is no longer
If i'm not wrong it will be synced once you try to access any
of the unsynced files, except if the file does not exist on the
first volume
That is not quite true, if all the modifications were performed from
the mountpoint, then it does not matter which server went down. If
files were removed
I live migrate the VM's to the node that is staying up, then
back
again when the reboot is complete.
2 questunes here ,
- what happen if the reboot is at night(self reboot of the
server) iv seen it happen
and nobody there to do the migration ? the all thing breaks ?
You can use things
Hi
there. I'm new to GlusterFS and really impressed with the feature set.
I'm looking to have four servers that also run the client, with each
client having replication for all clients. That way, I'll have four
servers with the same files, regardless of which server they're written
on. This way I
