>>>>> Amit K Arora (AKA) writes: AKA> Above we can see that block numbers from 68 to 502 are each covered by AKA> more than one extent (besides couple of holes, which also might be part AKA> of the same problem). AKA> Note: A "u" in extent[u] donates that this extent is AKA> uninitialized, and thus was created as part of preallocation and noone AKA> has written to it. An "i" signifies that the extent is initialized. AKA> I am trying to solve this issue currently. Any suggestions are more than AKA> welcome.. :) I'd write a simple function that check given leaf for consistency (in this case you need to check that every subsequent extent doesn't overlap previous one) and add this check in few points (before and after change). this worked very well, especially if all extents fit single block. thanks, Alex - To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
