On Sat, Aug 18, 2012 at 11:18:45AM +0200, Emmanuel Dreyfus wrote:
> The mess originates from dht_layout_normalize()/dht_layout_anomalies()
Further logging tells me this:
============ start dht_layout_anomalies ============
last_stop = -1, prev_stop = -1
i = 0, down = 0, missing = 0, misc = 0, hole_cnt = 0, overlap_cnt = 0
layout->list[0].start = 0, layout->list[0].stop = 0, layout->list[0].err = -1
i = 1, down = 0, missing = 1, misc = 0, hole_cnt = 0, overlap_cnt = 0
layout->list[1].start = 0, layout->list[1].stop = 0x7ffffffe,
layout->list[1].err = 0
=======> hole = 1, overlap = 0 <======
[dht-layout.c:599:dht_layout_normalize] 1-vndfs-dht: found anomalies
in /. holes=1 overlaps=0
I understand this code checks that the layout cover the whole space,
is that right? Then it must be upset that layout->list[0] does not cover
anything. Since the error is transcient, I susepct a race condition:
the layout would be filled after that check. Is it possible? Where is
the layout crafted?
--
Emmanuel Dreyfus
manu@xxxxxxxxxx
