Fix problems with array.size overflowing on large arrays.

array.size is 32bits and counts K.  So for arrays with
more than 4Terrabytes, it can overflow.
The correct number can be read from sysfs, but there are still
a few places that use array.size and risk truncation.  What is worse.
they compare a number of kilobytes with a number of sectors !!

So use get_component_size() to read the sysfs information, and be
more consistent about units.

1 files changed, 2 insertions, 0 deletions

diff --git a/ChangeLog b/ChangeLog
index fdf720d..fd42b4e 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,6 +1,8 @@
 Changes Prior to this release
     -   Avoid segfault when parsing /proc/mdstat with auto-read-only
 	arrays.
+    -   Fix problem with failing to add devices to v.large (>4TB) arrays,
+	cause by problems with device-size overflow.
 
 Changes Prior to 2.6.4 release
     -   Make "--create --auto=mdp" work for non-standard device names.