Re: gf-complete alignment constraints

On 01/12/2014 23:36, Kevin Greenan wrote: > No problem. Let me know if you need any help! Thanks ! When investigating this problem I stumbled upon exit(1) in gf-complete and came up with a patch to replace them with assert(0): https://github.com/ceph/gf-complete/pull/1/files When exit(1) is

Re: gf-complete alignment constraints

You can ignore this thread, the problem is not in gf-complete or jerasure ;-) Sorry for the noise On 01/12/2014 22:47, Loic Dachary wrote: > > > On 01/12/2014 22:01, Kevin Greenan wrote: >> Hey Loic, >> >> Makes sense. I can have a look tonight. > > I'm actually mistaken, confused the first a

Re: gf-complete alignment constraints

On 01/12/2014 22:01, Kevin Greenan wrote: > Hey Loic, > > Makes sense. I can have a look tonight. I'm actually mistaken, confused the first argument with the second one :-/ I'll keep looking. > > Thanks! > -kevin > > On Mon, Dec 1, 2014 at 11:15 AM, Loic Dachary >

gf-complete alignment constraints

Hi Kevin, I've hit the following stack trace (and I can reproduce it which is nice ;-) #0 __GI_exit (status=1) at exit.c:104 #1 0x718f3312 in gf_set_region_data (rd=0x7fffd9b8b0a0, gf=0x485dd40, src=0x4a7b31f, dest=0x4d25800, bytes=2048, val=143, xor=1, align=16) at erasure-code/jeras