Public bug reported:

Binary package hint: lvm2

Just installed a new server which has a hardware raid6 in it, on which a
lvm vg is set up.

It's a fresh Ubuntu-Server 7.10 Gutsy Gibbon install, with all current
updates.

Trying to add a new lv fails because device-mapper thinks that a device
is too small:

[EMAIL PROTECTED]:~# uname -a
Linux erebus 2.6.22-14-xen #1 SMP Tue Dec 18 07:06:28 UTC 2007 x86_64 GNU/Linux
[EMAIL PROTECTED]:~# lvm version
  LVM version:     2.02.26 (2007-06-15)
  Library version: 1.02.20 (2007-06-15)
  Driver version:  4.11.0
[EMAIL PROTECTED]:~# dmsetup version
Library version:   1.02.20 (2007-06-15)
Driver version:    4.11.0
[EMAIL PROTECTED]:~# pvs
  PV         VG    Fmt  Attr PSize PFree
  /dev/sdb1  raid6 lvm2 a-   4.09T 3.96T
[EMAIL PROTECTED]:~# ls /dev/mapper/
control  raid6-dom0  raid6-dom0--swap  raid6-domU--gutsy--disk  
raid6-domU--gutsy--swap
[EMAIL PROTECTED]:~# ls /dev/raid6
dom0  dom0-swap  domU-gutsy-disk  domU-gutsy-swap
[EMAIL PROTECTED]:~# lvcreate -v -n test -L 90G raid6
    Finding volume group "raid6"
    Archiving volume group "raid6" metadata (seqno 47).
    Creating logical volume test
    Creating volume group backup "/etc/lvm/backup/raid6" (seqno 48).
    Found volume group "raid6"
    Creating raid6-test
    Loading raid6-test table
  device-mapper: reload ioctl failed: Invalid argument
  Failed to activate new LV.
[EMAIL PROTECTED]:~# dmesg | tail -n 3
[27673.414059] device-mapper: table: device 8:17 too small for target
[27673.414071] device-mapper: table: 254:4: linear: dm-linear: Device lookup 
failed
[27673.414131] device-mapper: ioctl: error adding target to table
[EMAIL PROTECTED]:~# 

As seen above, there should be more than enough space in the vg to
create a 90GB lv.

Interestingly, lvm knows about the new lv:

[EMAIL PROTECTED]:~# lvdisplay -C
  LV              VG    Attr   LSize  Origin Snap%  Move Log Copy% 
  dom0            raid6 -wi-ao 10.00G                              
  dom0-swap       raid6 -wi-ao 32.00G                              
  domU-gutsy-disk raid6 -wi-ao  4.00G                              
  domU-gutsy-swap raid6 -wi-ao 64.00M                              
  test            raid6 -wi-d- 90.00G                              
[EMAIL PROTECTED]:~# 

but the state/Attr seems to be wrong.

device-mapper seems to know about the new lv:

[EMAIL PROTECTED]:~# ls /dev/mapper/
control  raid6-dom0  raid6-dom0--swap  raid6-domU--gutsy--disk  
raid6-domU--gutsy--swap  raid6-test

but not lvm itself:

[EMAIL PROTECTED]:~# ls /dev/raid6
dom0  dom0-swap  domU-gutsy-disk  domU-gutsy-swap
[EMAIL PROTECTED]:~# 

vgmknodes creates the appropriate link:
lrwxrwxrwx 1 root root 22 2008-01-15 23:31 test -> /dev/mapper/raid6-test
but the new lv is not usable.

[EMAIL PROTECTED]:~# mke2fs /dev/raid6/test 
mke2fs 1.40.2 (12-Jul-2007)
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.

[EMAIL PROTECTED]:~#


Any Ideas? Any information missing? I'm able to test some things out, since the 
server is not used productively atm.

** Affects: lvm2 (Ubuntu)
     Importance: Undecided
         Status: New

-- 
lvcreate fails to create new lv
https://bugs.launchpad.net/bugs/183359
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to