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

teh test3s tehtest3s at gmail.com
Thu Jan 8 01:04:50 UTC 2009


Package: lvm2
Severity: important

I am trying to create a 3 TB LVM logical volume in an LVM logical group that
has 3.2 TB of space available.

When I do:

  lvcreate -n bigstore --size 3T volgroup00

I get error:

  device-mapper: reload ioctl failed: Invalid argument
  Aborting. Failed to activate new LV to wipe the start of it.

However, it works when I do:

  lvcreate -n bigstore --size 1T volgroup00

My RAID controller is an HP SmartArray E200, with 5 SATA disks attached.

When I get the above error msg, dmesg output contains:

  [ 1983.464417] device-mapper: table: device 104:21 too small for target
  [ 1983.464417] device-mapper: table: 254:1: linear: dm-linear: Device
lookup failed
  [ 1983.464417] device-mapper: ioctl: error adding target to table
  [ 2053.045460] device-mapper: table: device 104:21 too small for target
  [ 2053.045460] device-mapper: table: 254:1: linear: dm-linear: Device
lookup failed

Here is some more information:

      ~# pvdisplay
        --- Physical volume ---
        PV Name               /dev/cciss/c0d0p1
        VG Name               volgroup00
        PV Size               195.31 GB / not usable 684.50 KB
        Allocatable           yes (but full)
        PE Size (KByte)       4096
        Total PE              49999
        Free PE               0
        Allocated PE          49999
        PV UUID               qiDCal-vQqw-N1lq-8bN3-D4q6-SI2I-8t2gNs

        --- Physical volume ---
        PV Name               /dev/cciss/c0d1p5
        VG Name               volgroup00
        PV Size               3.22 TB / not usable 2.79 MB
        Allocatable           yes
        PE Size (KByte)       4096
        Total PE              843200
        Free PE               843200
        Allocated PE          0
        PV UUID               wF9oyR-R0tf-bZeW-0es1-FhYK-f2g3-xS1Rd9



      ~# vgscan
        Reading all physical volumes.  This may take a while...
        Found volume group "volgroup00" using metadata type lvm2



      ~# vgdisplay
        --- Volume group ---
        VG Name               volgroup00
        System ID
        Format                lvm2
        Metadata Areas        2
        Metadata Sequence No  25
        VG Access             read/write
        VG Status             resizable
        MAX LV                0
        Cur LV                1
        Open LV               1
        Max PV                0
        Cur PV                2
        Act PV                2
        VG Size               3.41 TB
        PE Size               4.00 MB
        Total PE              893199
        Alloc PE / Size       49999 / 195.31 GB
        Free  PE / Size       843200 / 3.22 TB
        VG UUID               JWXg8s-LW8f-bQQY-3sLc-xOqY-5nPw-KncSpV



      ~# lvdisplay
        --- Logical volume ---
        LV Name                /dev/volgroup00/vol00
        VG Name                volgroup00
        LV UUID                nK5zJu-Jv3H-a01I-78gy-A96D-MvyQ-3RhNoA
        LV Write Access        read/write
        LV Status              available
        # open                 1
        LV Size                195.31 GB
        Current LE             49999
        Segments               1
        Allocation             inherit
        Read ahead sectors     auto
        - currently set to     256
        Block device           254:0


      ~# lvcreate -n bigstore --size 2.5T volgroup00
        device-mapper: reload ioctl failed: Invalid argument
        Aborting. Failed to activate new LV to wipe the start of it.



      ~# lvcreate -n bigstore --size 2T volgroup00
        device-mapper: reload ioctl failed: Invalid argument
        Aborting. Failed to activate new LV to wipe the start of it.



      ~# lvcreate -n bigstore --size 1.5T volgroup00
        device-mapper: reload ioctl failed: Invalid argument
        Aborting. Failed to activate new LV to wipe the start of it.



      ~# lvcreate -n bigstore --size 1T volgroup00
        Logical volume "bigstore" created



      ~# lvdisplay
        --- Logical volume ---
        LV Name                /dev/volgroup00/vol00
        VG Name                volgroup00
        LV UUID                nK5zJu-Jv3H-a01I-78gy-A96D-MvyQ-3RhNoA
        LV Write Access        read/write
        LV Status              available
        # open                 1
        LV Size                195.31 GB
        Current LE             49999
        Segments               1
        Allocation             inherit
        Read ahead sectors     auto
        - currently set to     256
        Block device           254:0

        --- Logical volume ---
        LV Name                /dev/volgroup00/bigstore
        VG Name                volgroup00
        LV UUID                p6If7Z-P34M-l24d-Wh3v-42t0-tIfZ-Kaq17s
        LV Write Access        read/write
        LV Status              available
        # open                 0
        LV Size                1.00 TB
        Current LE             262144
        Segments               1
        Allocation             inherit
        Read ahead sectors     auto
        - currently set to     256
        Block device           254:1




      ~# vgdisplay
        --- Volume group ---
        VG Name               volgroup00
        System ID
        Format                lvm2
        Metadata Areas        2
        Metadata Sequence No  32
        VG Access             read/write
        VG Status             resizable
        MAX LV                0
        Cur LV                2
        Open LV               1
        Max PV                0
        Cur PV                2
        Act PV                2
        VG Size               3.41 TB
        PE Size               4.00 MB
        Total PE              893199
        Alloc PE / Size       312143 / 1.19 TB
        Free  PE / Size       581056 / 2.22 TB
        VG UUID               JWXg8s-LW8f-bQQY-3sLc-xOqY-5nPw-KncSpV


      THERE IS STILL 2.22 TB FREE, ISN'T THERE ?!?!?!?!


      ~# lvcreate -n another --size 1T volgroup00
        device-mapper: reload ioctl failed: Invalid argument
        Aborting. Failed to activate new LV to wipe the start of it.



      ~# lvremove /dev/volgroup00/bigstore
      Do you really want to remove active logical volume "bigstore"? [y/n]:
y
      Logical volume "bigstore" successfully removed

      ~# lvcreate -n bigstore --size 3T volgroup00
      device-mapper: reload ioctl failed: Invalid argument Aborting.
      Failed to activate new LV to wipe the start of it.

      ~# lvcreate -n bigstore --size 2.5T volgroup00
      device-mapper: reload ioctl failed: Invalid argument Aborting.
      Failed to activate new LV to wipe the start of it.

      ~# lvcreate -n bigstore --size 2T volgroup00
      device-mapper: reload ioctl failed: Invalid argument Aborting.
      Failed to activate new LV to wipe the start of it.

      ~# lvcreate -n bigstore --size 1.5T volgroup00
      device-mapper: reload ioctl failed: Invalid argument Aborting.
      Failed to activate new LV to wipe the start of it.

      ~# lvcreate -n bigstore --size 1T volgroup00
      Logical volume "bigstore" created


-- System Information:
Debian Release: 5.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-1-686 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.alioth.debian.org/pipermail/pkg-lvm-maintainers/attachments/20090107/2e1be0c1/attachment.htm 


More information about the pkg-lvm-maintainers mailing list