[Gluster-users] glusterfs alternative ? :P

Keith Freedman freedman at FreeFormIT.com
Wed Jan 7 21:37:20 UTC 2009


At 07:11 AM 1/7/2009, you wrote:

>
>a_pirania at poczta.onet.pl napisa³(a):
>  >
>  >
>  > "Keith Freedman" <freedman at FreeFormIT.com> napisa³(a):
>  >  > At 05:15 AM 1/7/2009, a_pirania at poczta.onet.pl wrote:
>  >  > >"Keith Freedman" <freedman at FreeFormIT.com> napisa³(a):
>  >  > >  > At 04:28 AM 1/7/2009, a_pirania at poczta.onet.pl wrote:
>  >  > >  > >What errors are you getting? :-) We 
> surely want to fix any errors.
>  >  > >  > >
>  >  > >  > >Krishna
>  >  > >  > >
>  >  > >  > >
>  >  > >  > >You read thread "AFR self-heal problem" :)
>  >  > >  >
>  >  > >  >
>  >  > >  > make sure you're on the latest patch-level, I'm pretty sure those
>  >  > >  > problems have been resolved.
>  >  > >  > I ran into that same problem and it 
> was fixed the same day I reported it.
>  >  > >  >
>  >  > >  > Keith
>  >  > >  >
>  >  > >
>  >  > >Next thread "AFR not working ?" there is a
>  >  > >problem in glusterfs 1.4.0rc3 built on Dec 17 2008 15:34:25
>  >  > >Repository revision: glusterfs--mainline--3.0--patch-777
>  >  >
>  >  > well, rc3/patch 777 are very old.
>  >  > I'm running patch-824 (from tla) and the problem
>  >  > you're concerned with is not happening in my setup.
>  >  >
>  >  >
>  > Ok
>  > I check it
>
>
>ehhhhhh bug!
>
>2009-01-07 16:03:19 E 
>[afr-self-heal-data.c:778:afr_sh_data_fix] afr: 
>Unable to resolve conflicting data of 
>/blogdev/production/files/rupy1.jpg. Please 
>resolve manually by deleting the file 
>/blogdev/production/files/rupy1.jpg from all but 
>the preferred subvolume. Please consider 'option favorite-child <>'
>
>
>
>noc-test-2:/mnt/glusterfs# cat ./blogdev/production/files/rupy1.jpg | head -1
>cat: ./blogdev/production/files/rupy1.jpg: Input/output error
>
>glusterfs 1.4.0rc7 built on Jan  7 2009 15:00:10
>Repository revision: glusterfs--mainline--3.0--patch-814


not bug.. you need to read these error messages.
auto-heal can't figure out which file is the 
newest one, so instead of just picking and doing 
something bad, it's letting you fix it.
you can fix it by either deleting the file from 
all but the preferred volume OR you can add:
option favorite-child
to the gluster config.

if you choose to add option favorite-child  then 
it will always pick from that brick whenever there's an un resolvable conflict.





More information about the Gluster-users mailing list