FedoraForum.org - Fedora Support Forums and Community
Results 1 to 4 of 4
  1. #1
    Join Date
    Sep 2007
    Posts
    6

    device-mapper: reload ioctl failed: Invalid argument Failed to suspend LogVol00

    I hope this is the right forum.
    I've read hundreds of threads on this problem but they seem to be intermittent and the resolution has been using a different kernel version.
    I'm using the latest kernel but I still have this problem
    [root@fc11-64 ~]# rpm -q kernel
    kernel-2.6.29.6-217.2.8.fc11.x86_64
    [root@fc11-64 ~]# rpm -qa | grep lvm
    lvm2-2.02.48-2.fc11.x86_64
    system-config-lvm-1.1.9-1.fc11.noarch


    [root@fc11-64 ~]# lvresize -v -d -L 65.9375G /dev/VolGroup00/LogVol00
    Finding volume group VolGroup00
    Archiving volume group "VolGroup00" metadata (seqno 5).
    Extending logical volume LogVol00 to 65.94 GB
    Found volume group "VolGroup00"
    Found volume group "VolGroup00"
    Loading VolGroup00-LogVol00 table
    device-mapper: reload ioctl failed: Invalid argument
    Failed to suspend LogVol00
    Creating volume group backup "/etc/lvm/backup/VolGroup00" (seqno 6).

    [root@fc11-64 ~]# lvextend -v -d -L 65.9375G /dev/VolGroup00/LogVol00
    Finding volume group VolGroup00
    Archiving volume group "VolGroup00" metadata (seqno 5).
    Extending logical volume LogVol00 to 65.94 GB
    Found volume group "VolGroup00"
    Found volume group "VolGroup00"
    Loading VolGroup00-LogVol00 table
    device-mapper: reload ioctl failed: Invalid argument
    Failed to suspend LogVol00
    Creating volume group backup "/etc/lvm/backup/VolGroup00" (seqno 6).


    Running Logical Volume Manager gui and attempting to extend the volume results in the same error.

    [root@fc11-64 ~]# pvdisplay
    --- Physical volume ---
    PV Name /dev/sdb2
    VG Name VolGroup00
    PV Size 67.93 GB / not usable 24.13 MB
    Allocatable yes
    PE Size (KByte) 32768
    Total PE 2173
    Free PE 640
    Allocated PE 1533
    PV UUID eCuGyH-jV7L-Tgdg-JyYW-sWK1-ehZY-OLw0WS
    </cut>

    [root@fc11-64 ~]# vgdisplay
    --- Volume group ---
    VG Name VolGroup00
    System ID
    Format lvm2
    Metadata Areas 1
    Metadata Sequence No 5
    VG Access read/write
    VG Status resizable
    MAX LV 0
    Cur LV 2
    Open LV 0
    Max PV 0
    Cur PV 1
    Act PV 1
    VG Size 67.91 GB
    PE Size 32.00 MB
    Total PE 2173
    Alloc PE / Size 1533 / 47.91 GB
    Free PE / Size 640 / 20.00 GB
    VG UUID 7I9mBS-xzMJ-L1fC-7IT4-ckJq-g8r3-pv333k
    </cut>

    [root@fc11-64 ~]# lvdisplay
    --- Logical volume ---
    LV Name /dev/VolGroup00/LogVol01
    VG Name VolGroup00
    LV UUID ph5nOV-3cyI-fFNV-WlyQ-rDI8-dTsY-5FcWn2
    LV Write Access read/write
    LV Status available
    # open 0
    LV Size 1.97 GB
    Current LE 63
    Segments 1
    Allocation inherit
    Read ahead sectors auto
    - currently set to 256
    Block device 253:2
    </cut>

    --- Logical volume ---
    LV Name /dev/VolGroup00/LogVol00
    VG Name VolGroup00
    LV UUID ZGiTvh-XhRo-sLk5-bkJX-U30G-xkCD-rYszvt
    LV Write Access read/write
    LV Status available
    # open 0
    LV Size 45.94 GB
    Current LE 1470
    Segments 1
    Allocation inherit
    Read ahead sectors auto
    - currently set to 256
    Block device 253:3
    </cut>


    [root@fc11-64 ~]# tail -3 /var/log/messages
    Sep 10 20:55:46 fc11-64 kernel: device-mapper: table: device 8:18 too small for target
    Sep 10 20:55:46 fc11-64 kernel: device-mapper: table: 253:3: linear: dm-linear: Device lookup failed
    Sep 10 20:55:46 fc11-64 kernel: device-mapper: ioctl: error adding target to table

    [root@fc11-64 ~]# fdisk -l

    Disk /dev/sda: 107.3 GB, 107374182400 bytes
    255 heads, 63 sectors/track, 13054 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk identifier: 0x000d4599

    Device Boot Start End Blocks Id System
    /dev/sda1 * 1 26 204800 83 Linux
    Partition 1 does not end on cylinder boundary.
    /dev/sda2 26 13054 104651423+ 8e Linux LVM

    Disk /dev/sdb: 73.0 GB, 73014444032 bytes
    255 heads, 63 sectors/track, 8876 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk identifier: 0xd426be2d

    Device Boot Start End Blocks Id System
    /dev/sdb1 * 1 9 72261 83 Linux
    /dev/sdb2 10 6266 50259352+ 8e Linux LVM

    Disk /dev/dm-0: 102.9 GB, 102965968896 bytes
    255 heads, 63 sectors/track, 12518 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk identifier: 0x00000000

    Disk /dev/dm-0 doesn't contain a valid partition table

    Disk /dev/dm-1: 4194 MB, 4194304000 bytes
    255 heads, 63 sectors/track, 509 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk identifier: 0x00000000

    Disk /dev/dm-1 doesn't contain a valid partition table

    Disk /dev/dm-2: 2113 MB, 2113929216 bytes
    255 heads, 63 sectors/track, 257 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk identifier: 0x00000000

    Disk /dev/dm-2 doesn't contain a valid partition table

    Disk /dev/dm-3: 49.3 GB, 49325015040 bytes
    255 heads, 63 sectors/track, 5996 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk identifier: 0x00000000

    Disk /dev/dm-3 doesn't contain a valid partition table



    Anybody know what the problem is?
    TIA
    Hugh
    Last edited by HughB; 10th September 2009 at 12:05 PM.

  2. #2
    Join Date
    Nov 2007
    Location
    Falls Church, Virginia
    Posts
    3
    I am fighting LVM myself, but in a quick glance at your problem I would ask:

    Is LogVol00 / Volgroup00 part of your mounted operating system?
    You may have to boot from a recovery or live CD in order to take action on your root volume.

    You can't make changes while any part of the LVM is in use:
    cf. http://dailypackage.fedorabook.com/i...scue-Mode.html

    Also, Fedora11 trashes partition tables and overwrites whole disks with PV information, thus "fdisk -l" can not provide information about a device, i.e. no partition table.

    The only other option you can try doing is a "dd if=<device> count=4|od -c" and scan for the /etc/lvm/backup/<vg> information.

  3. #3
    Join Date
    Jan 2005
    Posts
    5,059
    lvextend -v -d -L 65.9375G /dev/VolGroup00/LogVol00 # <<=== Lvextend online is ok, but guessing the size in GB is not always easy.. Just leave off the size spec and it will use all the remaining VG freespace or
    specifiy it in PE's equal to the free PE's or less. (But then resize2fs becomes a problem, again leave off the spec and it will fill the LV.)



    VG Size 67.91 GB
    PE Size 32.00 MB #<<<==== may not be an exact multiple of.-L 65.9375G
    Total PE 2173
    Alloc PE / Size 1533 / 47.91 GB
    Free PE / Size 640 / 20.00 GB <<==== you have 32 x 640 free., 67.91, but there is overhead.
    VG UUID 7I9mBS-xzMJ-L1fC-7IT4-ckJq-g8r3-pv333k

    SJ

    P. S. If the space is on another PV then add that to the lvextend /dev/mapper/VG-LV /dev/sdg1 (whatever it is called.)
    Last edited by SlowJet; 15th October 2009 at 09:06 PM.
    Do the Math

  4. #4
    Join Date
    Jan 2005
    Posts
    5,059
    Quote Originally Posted by kao650
    I am fighting LVM myself, but in a quick glance at your problem I would ask:

    Is LogVol00 / Volgroup00 part of your mounted operating system?
    You may have to boot from a recovery or live CD in order to take action on your root volume.

    You can't make changes while any part of the LVM is in use:
    cf. http://dailypackage.fedorabook.com/i...scue-Mode.html

    Also, Fedora11 trashes partition tables and overwrites whole disks with PV information, thus "fdisk -l" can not provide information about a device, i.e. no partition table.

    The only other option you can try doing is a "dd if=<device> count=4|od -c" and scan for the /etc/lvm/backup/<vg> information.
    F10 (maybe) and f11 and F12 can be extended online.
    PV can be on a partition type 8e. The meta data is within the PV.
    Fedora default install used sda2 for the PV.

    SJ
    Do the Math

Similar Threads

  1. Replies: 0
    Last Post: 19th November 2006, 05:43 PM
  2. /dev/mapper/VolGroup00-LogVol00 - question
    By Numenor in forum Using Fedora
    Replies: 4
    Last Post: 1st September 2006, 10:49 PM
  3. Replies: 1
    Last Post: 29th November 2005, 04:31 AM
  4. Error enabling swap device - invalid argument
    By stodge in forum Installation, Upgrades and Live Media
    Replies: 4
    Last Post: 12th January 2005, 12:19 AM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •