Bug#511171: Related IRC conversation

[teh test3s]

   1.

   [2009/01/07 18:20:50] <test3s> so I am running debian 5.0
2.6.26-1-686 kernel.  I have an LVM logical volume that lvdisplay
shows is 3.22 TB called /dev/volgroup00/vol01.  When I try to mke2fs
-j /dev/volgroup00/vol01, I get "mke2fs: Device size reported to be
zero.  Invalid partition specified, or partition table wasn't reread
after running fdisk, due to a modified partition being busy and in
use.  You may need to reboot to re-read your partition table."

   2.

   [2009/01/07 18:23:33] <dutchfish> test3s, delve into pvcreate
vgcreate and then you can create with lvcreate

   3.

   [2009/01/07 18:24:19] <dutchfish> test3s, after that you can install your FS

   4.

   [2009/01/07 18:25:46] <test3s> dutchfish: I already have a logical
volume /dev/volgroup00/vol01 - shouldn't I be able to mke2fs -j
/dev/volgroup00/vol01 ?

   5.

   [2009/01/07 18:26:06] <dutchfish> test3s, no

   6.

   [2009/01/07 18:26:34] <dutchfish> test3s, phys vol, vol group,
logocal volume, FS in that order

   7.

   [2009/01/07 18:28:16] <dutchfish> test3s,
http://www.debian-administration.org/articles/410

   8.

   [2009/01/07 18:32:12] <test3s> dutchfish: I already went through
that link - my volume group (found via vgscan) is volgroup00.  my
physical volume (found via pvdisplay) is /dev/cciss/c0d1p5, and is in
volume group volgroup00.  my logical volume (found via lvdisplay) is
/dev/volgroup00/vol01.  I don't understand...

   9.

   [2009/01/07 18:33:02] <dutchfish> test3s, normally you work through
the mapper, so can you paste to pastebin th eoutput of vgdisplay and
lvdisplay please?

   10.

   [2009/01/07 18:45:03] <test3s> when I do: lvcreate -n storage -l
100%FREE volgroup00, I get "device-mapper: reload ioctl failed:
Invalid argument  Aborting. Failed to activate new LV to wipe the
start of it."

   11.

   [2009/01/07 18:46:15] <test3s> it's as if debian or my raid
controller can't handle creating a 3TB logical volume

   12.

   [2009/01/07 18:47:53] <dutchfish> test3s, using etch or lenny?

   13.

   [2009/01/07 18:50:36] <dutchfish> test3s, i believe the max size of
a single lvm partition in Etch is  16TB on 32 bit systems

   14.

   [2009/01/07 18:52:03] <dutchfish> test3s, can you post your
lvdisplay vgdisplay? /msf dpkg pastebin

   15.

   [2009/01/07 18:52:18] <dutchfish> test3s, er: /msg dpkg pastebin

   16.

   [2009/01/07 18:58:32] <test3s> dutchfish: http://paste.debian.net/25493/

   17.

   [2009/01/07 19:01:48] <dutchfish> test3s, did you try to remove th
elv and then create it again?

   18.

   [2009/01/07 19:02:57] <dutchfish> test3s, it looks like during
creating the 1st LV, something went bad

   19.

   [2009/01/07 19:06:16] <test3s> dutchfish: http://paste.debian.net/25494/

   20.

   [2009/01/07 19:07:13] <dutchfish> test3s, how many disks? and how
are they connected through controllers?

   21.

   [2009/01/07 19:09:58] <dutchfish> test3s, oh wait. Did you edit the
partition table AFTER creating the physical volume?

   22.

   [2009/01/07 19:10:10] <test3s> dutchfish: 5 SATA disks attached to
a single HP SmartArray E200 controller.

   23.

   [2009/01/07 19:10:20] <dutchfish> test3s, ok

   24.

   [2009/01/07 19:10:30] <folken> test3s: let me guess an ml-110? :)

   25.

   [2009/01/07 19:10:45] <test3s> folken: not sure.

   26.

   [2009/01/07 19:14:15] <dutchfish> test3s, did you take a close look
at dmesg output? this could be hardware related, and what kernel are
you running?

   27.

   [2009/01/07 19:14:58] <dutchfish> test3s, its not lvm2 it candle
handle much bigger setups hands down

   28.

   [2009/01/07 19:17:16] <test3s> I am running debian 5.0 with
2.6.26-1-686 kernel.

   29.

   [2009/01/07 19:18:29] <dutchfish> test3s, i suspect its not a lvm2
nor kernel issue but the driver, could you take a look at dmesg
output?

   30.

   [2009/01/07 19:18:29] <test3s> dmesg shows "device-mapper: table:
device 104:21 too small for target" and "device-mapper: table: 254:1:
linear: dm-linear: Device lookup failed"

   31.

   [ 1983.464417] device-mapper: table: device 104:21 too small for target

   32.

   [ 1983.464417] device-mapper: table: 254:1: linear: dm-linear:
Device lookup failed

   33.

   [2009/01/07 19:19:03] <dutchfish> test3s, there is your problem,
solving it is another thing

   34.

   [2009/01/07 19:19:12] <test3s> that error msg is displayed once for
every time I tried and failed to create a logical volume past 1.25 TB
or so.

   35.

   [2009/01/07 19:19:35] <dutchfish> test3s, right

   36.

   [2009/01/07 19:21:15] <dutchfish> test3s, Is it possible that you
are using the wrong target type, e.g. RAID0/1/5?

   37.

   [2009/01/07 19:21:55] <dutchfish> test3s, cat /proc/mdstat would reveal that

   38.

   [2009/01/07 19:27:11] <test3s> dutchfish: ~# cat /proc/mdstat:
cat: /proc/mdstat: No such file or directory
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.alioth.debian.org/pipermail/pkg-lvm-maintainers/attachments/20090107/b8afd4e0/attachment.htm