LVM extend volume problem

Discussion in 'Technical' started by gacain, Nov 24, 2008.

  1. gacain

    gacain New Member

    Hello,

    I'm wondering if anyone here might have time to help me out with a problem I'm having. This weekend, while trying to extend a logical volume on a RedHat Enterprise server (ES release 4 Nahant update 3), I get the following error:

    [[email protected] ~]# lvextend -L+10G /dev/VolGroupFiles/public
    Extending logical volume public to 20.00 GB
    device-mapper: deps ioctl failed: Invalid argument
    _deps: task run failed for (253:5)
    Failed to add device (253:5) to dtree
    Failed to suspend public

    The same error occurs with all logical volumes. As well, I get a similar error when trying to remove a volume:

    [[email protected] ~]# lvremove /dev/VolGroupFiles/test
    Do you really want to remove active logical volume "test"? [y/n]: y
    device-mapper: deps ioctl failed: Invalid argument
    _deps: task run failed for (253:9)
    Failed to add device (253:9) to dtree
    Unable to deactivate logical volume "test"


    Any insight as to how I might be able to resolve this would be very, very much appreciated.

    Thanks in advance.

    Regards,

    Greg
     
  2. falko

    falko Super Moderator ISPConfig Developer

    Are there any errors in your logs?

    Maybe it's a broken hard drive?
     
  3. gacain

    gacain New Member

    Hi,

    Thanks for responding.

    Looking in /var/log/messages all I'm seeing that may pertain to this is:

    messages.2:Nov 22 13:06:30 localhost kernel: device-mapper: one of name or uuid must be supplied, cmd(11)

    All hard drives seem to be working fine in this server.

    Any ideas?

    Thanks again.

    G
     
  4. sjau

    sjau Local Meanie Moderator

    how about
    Code:
    lvextend -L +10G /dev/VolGroupFiles/public
    
    ?
     
  5. gacain

    gacain New Member

    Hi sjau,

    Thanks for posting. I've actually tried that, and also:

    lvextend -L30G /dev/VolGroupFiles/public

    and receive the same error in all cases.

    Another thing that I noticed today - when creating a new lv, the file /dev/mapper/VolGroupFiles-test is created but the link /dev/VolGroupFiles/test is not.

    Any further suggestions would be very much appreciated.

    G
     
  6. sjau

    sjau Local Meanie Moderator

    what's the output of
    Code:
    vgdisplay -A 
    
     
  7. gacain

    gacain New Member

    Hi -

    Here it is:

    [[email protected] ~]# vgdisplay -A
    --- Volume group ---
    VG Name VolGroupFiles
    System ID
    Format lvm2
    Metadata Areas 1
    Metadata Sequence No 23
    VG Access read/write
    VG Status resizable
    MAX LV 0
    Cur LV 12
    Open LV 9
    Max PV 0
    Cur PV 1
    Act PV 1
    VG Size 956.33 GB
    PE Size 16.00 MB
    Total PE 61205
    Alloc PE / Size 37760 / 590.00 GB
    Free PE / Size 23445 / 366.33 GB
    VG UUID j6KxN9-kDac-e8BW-Aru5-mxC2-y0oh-ofKJkq

    --- Volume group ---
    VG Name VolGroup00
    System ID
    Format lvm2
    Metadata Areas 2
    Metadata Sequence No 8
    VG Access read/write
    VG Status resizable
    MAX LV 0
    Cur LV 6
    Open LV 6
    Max PV 0
    Cur PV 2
    Act PV 2
    VG Size 33.59 GB
    PE Size 32.00 MB
    Total PE 1075
    Alloc PE / Size 832 / 26.00 GB
    Free PE / Size 243 / 7.59 GB
    VG UUID tqL4pR-qw7C-ug0E-vaVV-9znZ-zp7p-jI36M0

    Thanks.

    G
     
  8. sjau

    sjau Local Meanie Moderator

    how about:

    Code:
    lvextend -l +23445 /dev/.../....
    lvextend -l +243 /dev/.../....
    
    that should expand it to full size.
     

Share This Page