Martin Lui <linuxdevel@xxxxxxxxxxxxxx> writes: > I ran into a similar situation as described in your thread (ack in Jun 2008): > http://marc.info/?l=linux-raid&m=121381509915920&w=2 > > First off, thank you both for your time to make this feature work. Since > I've increased the partition size of my RAID partition, I too needed to > grow my array and component devices. To do that, I attempted to use the > feature implemented in this patch: > http://marc.info/?l=linux-raid&m=121434960912711&w=2 [...] > However, it seems that the value applied by this method is half the > actual/correct value. Hi Martin. I'm afraid I haven't used this feature with recent kernels because the structure of our storage system changed so as not to require it. At the time, it definitely worked correctly, updating the component size at runtime, but I think there has been some work to unify the units (512 byte sectors vs 1kb blocks) of the various internals of the md driver since then. Perhaps this code wasn't updated to match the units change elsewhere? It's quite rarely used I think. Do you see this behaviour for both metadata formats 0.90 and 1.x? Best wishes, Chris. -- 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
