Bug#306200: unit consistency in lvm

[Daniel Kahn Gillmor]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I agree that consistency and clarity of units is important in LVM and
any other block device management tool.  It's weird to see things
like:

monkey:~# vgs --units G vg_troop0
  VG       #PV #LV #SN Attr   VSize   VFree
  vg_troop0   1   0   0 wz--n- 750.16G 750.16G
monkey:~# lvcreate --size 700G --name home vg_troop0
  Insufficient free extents (178851) in volume group vg_troop0: 179200 required
monkey:~#

FWIW, the section on --units in "man 8 vgs" sounds really good:

   --units hsbkmgtHKMGT
          All  sizes  are  output  in these  units:  (h)uman-readable,
          (s)ectors,  (b)ytes, (k)ilobytes,  (m)egabytes, (g)igabytes,
          (t)erabytes.   Capitalise to  use multiples  of  1000 (S.I.)
          instead  of  1024.  Can  also  specify  custom (u)nits  e.g.
          --units 3M

If these units were used consistently across the entire lvm2 suite, it
would make the tools more accessible.  This may be more of a bug for
upstream, though.  i'm not sure.

Thanks for maintaining lvm for debian,

	--dkg
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8+ <http://mailcrypt.sourceforge.net/>

iD8DBQFFpGMriXTlFKVLY2URAtTdAJ4+kaSkGQW104Fa73U4572xrJYAMgCgjUd1
TQoiTaqEEQan7d7c9J0XHSk=
=iYcf
-----END PGP SIGNATURE-----