Re: [Gluster-users] split brain recovery 3.3.0
Dear Patric, That seemed to make the trick because we can now see the file and access it. Is there any place where it could be documented? Thanks a lot, Samuel On 8 March 2013 10:40, Patric Uebele wrote: > Hi Samuel, > > can you try to drop caches on the clients: > > “echo 3 > /proc/sys/vm/drop_caches” > > /Patric > > On Fri, 2013-03-08 at 10:13 +0100, samuel wrote: > > No one around can help with this situation? > > > > The file finally got "corrupted" and it's impossible to read from any > > of the current mounted native gluster clients. > > > > Reading the attributes, all flags are set as 0: > > > > # file: dd29900f215b175939816f94c907a31b > > trusted.afr.storage-client-6=0x > > trusted.afr.storage-client-7=0x > > trusted.gfid=0x59311906edf04464be5f00f505b3aebb > > trusted.storage-stripe-1.stripe-count=0x3200 > > trusted.storage-stripe-1.stripe-index=0x3100 > > trusted.storage-stripe-1.stripe-size=0x31333130373200 > > > > so there should not be read as split brain from clients but we got the > > following logs: > > "split brain detected during lookup of" > > > > thanks in advance, > > Samuel. > > > > > > On 4 March 2013 14:37, samuel wrote: > > Hi folks, > > > > We have detected a split-brain on 3.3.0 stripped replicated 8 > > nodes cluster. > > We've followed the instructions from: > > > http://www.gluster.org/2012/07/fixing-split-brain-with-glusterfs-3-3/ > > and we've manually recovered the information. > > > > The problem is that we've got 4 gluster native clients and > > from 2 of them we got > > 0-storage-replicate-3: failed to open as split brain seen, > > returning EIO > > but from 2 of them we can access the recovered file. > > > > We're this information locally storage on clients so we can > > "update" all of them and recover the information in a > > "coherent" manner? > > > > Thanks a lot in advance, > > Samuel. > > > > ___ > > Gluster-users mailing list > > Gluster-users@gluster.org > > http://supercolony.gluster.org/mailman/listinfo/gluster-users > > -- > Patric Uebele > Solution Architect Storage > > Red Hat GmbH > Technopark II, Haus C > Werner-von-Siemens-Ring 14 > 85630 Grasbrunn > Germany > > Office:+49 89 205071-162 > Cell: +49 172 669 14 99 > mailto:patric.ueb...@redhat.com > > gpg keyid: 48E64CC1 > gpg fingerprint: C63E 6320 A03B 4410 D208 4EE7 12FC D0E6 48E6 4CC1 > > > Reg. Adresse: Red Hat GmbH, Werner-von-Siemens-Ring 14, 85630 Grasbrunn > Handelsregister: Amtsgericht Muenchen HRB 153243 > Geschaeftsfuehrer: Mark Hegarty, Charlie Peters, Michael Cunningham, > Charles Cachera > ___ Gluster-users mailing list Gluster-users@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-users
Re: [Gluster-users] split brain recovery 3.3.0
Hi Samuel, can you try to drop caches on the clients: “echo 3 > /proc/sys/vm/drop_caches” /Patric On Fri, 2013-03-08 at 10:13 +0100, samuel wrote: > No one around can help with this situation? > > The file finally got "corrupted" and it's impossible to read from any > of the current mounted native gluster clients. > > Reading the attributes, all flags are set as 0: > > # file: dd29900f215b175939816f94c907a31b > trusted.afr.storage-client-6=0x > trusted.afr.storage-client-7=0x > trusted.gfid=0x59311906edf04464be5f00f505b3aebb > trusted.storage-stripe-1.stripe-count=0x3200 > trusted.storage-stripe-1.stripe-index=0x3100 > trusted.storage-stripe-1.stripe-size=0x31333130373200 > > so there should not be read as split brain from clients but we got the > following logs: > "split brain detected during lookup of" > > thanks in advance, > Samuel. > > > On 4 March 2013 14:37, samuel wrote: > Hi folks, > > We have detected a split-brain on 3.3.0 stripped replicated 8 > nodes cluster. > We've followed the instructions from: > http://www.gluster.org/2012/07/fixing-split-brain-with-glusterfs-3-3/ > and we've manually recovered the information. > > The problem is that we've got 4 gluster native clients and > from 2 of them we got > 0-storage-replicate-3: failed to open as split brain seen, > returning EIO > but from 2 of them we can access the recovered file. > > We're this information locally storage on clients so we can > "update" all of them and recover the information in a > "coherent" manner? > > Thanks a lot in advance, > Samuel. > > ___ > Gluster-users mailing list > Gluster-users@gluster.org > http://supercolony.gluster.org/mailman/listinfo/gluster-users -- Patric Uebele Solution Architect Storage Red Hat GmbH Technopark II, Haus C Werner-von-Siemens-Ring 14 85630 Grasbrunn Germany Office:+49 89 205071-162 Cell: +49 172 669 14 99 mailto:patric.ueb...@redhat.com gpg keyid: 48E64CC1 gpg fingerprint: C63E 6320 A03B 4410 D208 4EE7 12FC D0E6 48E6 4CC1 Reg. Adresse: Red Hat GmbH, Werner-von-Siemens-Ring 14, 85630 Grasbrunn Handelsregister: Amtsgericht Muenchen HRB 153243 Geschaeftsfuehrer: Mark Hegarty, Charlie Peters, Michael Cunningham, Charles Cachera smime.p7s Description: S/MIME cryptographic signature ___ Gluster-users mailing list Gluster-users@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-users
Re: [Gluster-users] split brain recovery 3.3.0
No one around can help with this situation? The file finally got "corrupted" and it's impossible to read from any of the current mounted native gluster clients. Reading the attributes, all flags are set as 0: # file: dd29900f215b175939816f94c907a31b trusted.afr.storage-client-6=0x trusted.afr.storage-client-7=0x trusted.gfid=0x59311906edf04464be5f00f505b3aebb trusted.storage-stripe-1.stripe-count=0x3200 trusted.storage-stripe-1.stripe-index=0x3100 trusted.storage-stripe-1.stripe-size=0x31333130373200 so there should not be read as split brain from clients but we got the following logs: "split brain detected during lookup of" thanks in advance, Samuel. On 4 March 2013 14:37, samuel wrote: > Hi folks, > > We have detected a split-brain on 3.3.0 stripped replicated 8 nodes > cluster. > We've followed the instructions from: > http://www.gluster.org/2012/07/fixing-split-brain-with-glusterfs-3-3/ > and we've manually recovered the information. > > The problem is that we've got 4 gluster native clients and from 2 of them > we got > 0-storage-replicate-3: failed to open as split brain seen, returning EIO > but from 2 of them we can access the recovered file. > > We're this information locally storage on clients so we can "update" all > of them and recover the information in a "coherent" manner? > > Thanks a lot in advance, > Samuel. > ___ Gluster-users mailing list Gluster-users@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-users
[Gluster-users] split brain recovery 3.3.0
Hi folks, We have detected a split-brain on 3.3.0 stripped replicated 8 nodes cluster. We've followed the instructions from: http://www.gluster.org/2012/07/fixing-split-brain-with-glusterfs-3-3/ and we've manually recovered the information. The problem is that we've got 4 gluster native clients and from 2 of them we got 0-storage-replicate-3: failed to open as split brain seen, returning EIO but from 2 of them we can access the recovered file. We're this information locally storage on clients so we can "update" all of them and recover the information in a "coherent" manner? Thanks a lot in advance, Samuel. ___ Gluster-users mailing list Gluster-users@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-users
