[Gluster-users] Recovery from network failure

[Georgecooldude]

Without doing a reboot of one of the servers I don't seem to be able to
force replication again. I just end up with a partial file.

I'm starting gluster like this:
sudo glusterfs -f /etc/glusterfs/glusterfs-client.vol /mnt/glusterfs
sudo glusterfsd -f /etc/glusterfs/glusterfs-server.vol

And do the following to try and trigger it to replicate
sudo ls -alRh /mnt/glusterfs/
sudo ls -alRh /data/export
sudo ls -alRh /data/export-ns

Am I missing something?

On Sun, Sep 20, 2009 at 12:09 AM, Liam Slusser <lslusser at gmail.com> wrote:

> You need to force replication to happen...ie "ls -alR" on your gluster
> mount.
>
> liam
>
>
> On Sat, Sep 19, 2009 at 1:57 PM, Georgecooldude
> <georgecooldude at gmail.com> wrote:
> > Hi Guys
> >
> > I've been trying GlusterFS out today. I'm using Ubuntu 8 LTS, and Gluster
> > 2.0.6. In my test lab I have two servers configured to mirror each other.
> > Everything there works fine.
> >
> > However during failover testing I moved a 1GB image to the shared mount
> > point on server01. I watched about 250mb of data get replicated to
> server02
> > and then pulled the network cable out of server 02. When I plugged the
> cable
> > back in about 1 minute later I was expecting the file to continue
> > replicating however it didn't. Instead server02 got a corrupt 250mb file.
> >
> > Are there any steps that need to be taken to cover a scenario like this?
> >
> > Thanks in advance
> >
> > George
> >
> > _______________________________________________
> > Gluster-users mailing list
> > Gluster-users at gluster.org
> > http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
> >
> >
>