If I understand the Compendium (also known as mdadm manpage :-) ) the intent-logging bitmap is stored near the superblock when the name "internal" is specified. Does this mean that it'll be in the 128KB area of the superblock? If so, what happens if there isn't enough space? This is likely for medium-to-large arrays, say 500+GB with the default chunk 4K. About the size of the bitmap-chunk, wouldn't it be better if it were the size of a stripe? I ask this because I thought all IO to an array was done in multiples of the stripe size even if the write request is smaller. What's the influence of intent-logging in the performance of a raid5 array? It seems that it'll increase the number of writes, so a degradation is likely, no? This is important to decide if intent-logging is worth. I'd think that it's only worth for machines that crash often and leave the array dirty. - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
