Michał Przyłuski wrote:
Hello,
2009/10/25 Bart Kus <me@xxxxxxxx>:
# mdadm --detail /dev/md4
/dev/md4:
Version : 1.02
Creation Time : Sun Aug 10 23:41:49 2008
Raid Level : raid6
Array Size : 15628094464 (14904.11 GiB 16003.17 GB)
Used Dev Size : 3907023616 (3726.03 GiB 4000.79 GB)
...
# mdadm --examine /dev/sdc1
/dev/sdc1:
...
Avail Dev Size : 3907023730 (1863.01 GiB 2000.40 GB)
Array Size : 31256188928 (14904.11 GiB 16003.17 GB)
Used Dev Size : 3907023616 (1863.01 GiB 2000.40 GB)
Mostly likely cause is mdadm bug. Please let us know what's mdadm
version, but I'd suggest getting the newest one, and just seeing if
the output is correct. If I recall correctly, it's a bug related to a
sector<->bytes change in output generating code. Not dangerous. It was
brought to list's attention a while ago, I suppose it might've been in
2.6.7? From what I have installed here right now .4 and .9 are okay,
and .7 is just wrong.
And, as an aside comment, I think that some values of --detail,
--examine and cat /proc/mdstat are not always what you'd expect during
ongoing reshape. So if anything else is inconsistent right now, you
might want to wait.
Cheers,
Mike
--
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
Excellent! I'm running mdadm 2.6.8. I compiled 2.6.9 in /tmp/ and when
using that binary, it does show the correct size. When Gentoo decides
to upgrade, this little problem should fix itself.
Thanks!
--Bart
--
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
