[Gluster-users] How to re-sync

[Tejas N. Bhise]

Yes. Replace the binaries and restart.

----- Original Message -----
From: "Stephan von Krawczynski" <skraw at ithnet.com>
To: "Tejas N. Bhise" <tejas at gluster.com>
Cc: "Ed W" <lists at wildgooses.com>, "Gluster Users" <gluster-users at gluster.org>
Sent: Tuesday, March 9, 2010 7:33:02 PM GMT +05:30 Chennai, Kolkata, Mumbai, New Delhi
Subject: Re: [Gluster-users] How to re-sync

We run 2.0.9 currently. Can we compile & install 3.X simply over 2.X, or do we
need to re-create the replication (via self-heal), or even copy the data from
scratch to an empty exported replication glusterfs?




On Mon, 8 Mar 2010 23:45:05 -0600 (CST)
"Tejas N. Bhise" <tejas at gluster.com> wrote:

> Ed, Chad, Stephen,
> 
> We believe we have fixed all ( known ) problems with self-heal 
> in the latest releases and hence we would be very interested in 
> getting diagnostics if you can reproduce the problem or see it 
> again frequently. 
> 
> Please collect the logs by running the client and servers with 
> log level TRACE and then reproducing the problem.
> 
> Also collect the backend extended attributes of the file on 
> both servers before self-heal was triggered. This command can be 
> used to get that info:
> 
> # getfattr -d -m '.*' -e hex <filename>
> 
> Thank you for you help to debug if any new problem shows up.
> Feel free to ask if you have any queries about this.
> 
> Regards,
> Tejas.