On 4/14/06, Andrei Popescu <[EMAIL PROTECTED]> wrote: > > > > > On Wed, 2006-04-12 at 12:32 -0400, Matthias Julius wrote: > > > > >> Yes, there is. As example here is part of the output of mdadm: > > > > >> > > > > >> Array Size : 468872448 (447.15 GiB 480.13 GB) > > > > >> Device Size : 156290816 (149.05 GiB 160.04 GB) > > > > >> ^^^ ^^ > > > > >> > > > > >> Note there is GiB (gibibyte) which is 1024 MiB (mebibyte) and there > > > > >> is > > > > >> GB (gigabyte) which is 1000 MB (megabyte). > It was just right. This is more in detail: > > 156290816(kiB) * 1024 = 160041795584 bytes > > 160041795584/1000/1000/1000 ~= 160.04 GB > > or > > 160041795584/1024/1024/1024 ~= 149.05 GiB
This is an example of how just slightly better command output or logging could save many man-hours of confusion or explanation. Since the mdadm program displays the values in two human readable forms (GB and GiB), it could also print the first number as a raw count of bytes (with the suffix "bytes") to make the size of the array entirely clear and precise to the user.
