Bug#511171: lvm2: Unable to use full 3.2 TB of LVM LG on HP SmartArray E200

[teh test3s]

That's a GREAT question.  The really weird thing is that the RAID array in
question *does* actually have 3.2 TB of free space in it!  (5 x 750GB SATA
in RAID 5 array).  I am completely baffled.
~# blockdev --report
RO    RA   SSZ   BSZ   StartSec     Size    Device
rw   256   512  4096          0  409599360  /dev/cciss/c0d0
rw   256   512   512         63  409593177  /dev/cciss/c0d0p1
rw   256   512  4096          0 6915815280  /dev/cciss/c0d1
rw   256   512  1024         63     497952  /dev/cciss/c0d1p1
rw   256   512  4096     498015    7807590  /dev/cciss/c0d1p2
rw   256   512  1024    8305605          2  /dev/cciss/c0d1p3
rw   256   512   512    8305668 2612532821  /dev/cciss/c0d1p5
rw   256   512  4096          0  409591808  /dev/dm-0


On Wed, Jan 7, 2009 at 8:35 PM, Alasdair G Kergon <agk at redhat.com> wrote:

> On Wed, Jan 07, 2009 at 08:23:36PM -0500, teh test3s wrote:
> >   PV                VG         Fmt  Attr PSize   PFree DevSize PV UUID
> >   /dev/cciss/c0d1p5 volgroup00 lvm2 a-     3.22T 2.22T   1.22T
> > wF9oyR-R0tf-bZeW-0es1-FhYK-f2g3-xS1Rd9
>
> So that's what you need to explain:
>
>  How come LVM thinks that device is 3.22T while it's really only 1.22T ?
>
> Presumably blockdev --getsize will tell you the same.
>
> IOW It's not an LVM issue.  Check your cciss partitioning.
>
> Alasdair
> --
> agk at redhat.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.alioth.debian.org/pipermail/pkg-lvm-maintainers/attachments/20090107/d50c39da/attachment.htm