LVM2 can not wake up suspended logical volume












4














Read my story below.



I'm using LVM2 with following information:



Scan for VG:



# vgs
VG #PV #LV #SN Attr VSize VFree
unix 1 1 0 wz--n- 115.00g 45.00g


Scan for LV



# lvs
LV VG Attr LSize Origin Snap% Move Log Copy% Convert
work unix -wi-s- 70.00g


Attempt to activate VG, LV



# vgchange -ay
device-mapper: resume ioctl failed: Invalid argument
Unable to resume unix-work (254:1)
1 logical volume(s) in volume group "unix" now active


Check LV activated or not



# lvdisplay 
/dev/mapper/unix-work: open failed: No such file or directory
--- Logical volume ---
LV Name /dev/unix/work
VG Name unix
LV UUID HzzTTr-rX2d-w1dP-NEQL-QksJ-rmHW-jMTxO7
LV Write Access read/write
LV Status NOT available
LV Size 70.00 GiB
Current LE 17920
Segments 2
Allocation inherit
Read ahead sectors auto


Because of last command end with error: "/dev/mapper/unix-work: open failed: No such file or directory"
Then I have to run vgmknodes to manual create /dev/ nodes as below



# vgmknodes 
The link /dev/unix/work should had been created by udev but it was not found. Falling back to direct link creation.


Now it look like better with status "suspended"



# lvdisplay 
--- Logical volume ---
LV Name /dev/unix/work
VG Name unix
LV UUID HzzTTr-rX2d-w1dP-NEQL-QksJ-rmHW-jMTxO7
LV Write Access read/write
LV Status suspended
# open 0
LV Size 70.00 GiB
Current LE 17920
Segments 2
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:1


Attempt to mount LV:



# mount /dev/unix/work /mnt/
mount: /dev/mapper/unix-work already mounted or /mnt/ busy


Message from dmesg:



[ 1527.566964] device-mapper: table: 254:1: sda3 too small for target: start=94372224, len=136306688, dev_size=224606491


So, my question is: how can I wake up LV to mount it or use dd command to get data from LVM partition?



Thanks in advanced!










share|improve this question






















  • 1. try update the follwing packges kernel , device-mapper, lvm2 . 2. deactivate with vgchange -an , then activate with vgchange -ay.
    – Hanan N.
    Nov 28 '11 at 6:00










  • Already read on LVM FAQ but not tried yet, I'm using live cd of Arch Bang so can not make a kernel update. I think it is not related to kernel since I use live cd before & after this problem happen. FYI: uname -a Linux archbang 3.0-ARCH #1 SMP PREEMPT Wed Oct 19 10:27:51 CEST 2011 x86_64 Intel(R) Core(TM) i5-2410M CPU @ 2.30GHz GenuineIntel GNU/Linux
    – tiger2wander
    Nov 28 '11 at 8:44












  • The output from pvdisplay and fdisk -lu /dev/sda would be helpful. This part makes it sound like your partition holding the PV has shrunk, which is a big problem: sda3 too small for target: start=94372224, len=136306688, dev_size=224606491
    – psusi
    Nov 28 '11 at 15:45










  • @Hannan: I have installed Arch Linux to another partition and using latest linux kernel: Linux hydrogen 3.1.2-1-ARCH #1 SMP PREEMPT Tue Nov 22 09:17:56 CET 2011 x86_64 Intel(R) Core(TM) i5-2410M CPU @ 2.30GHz GenuineIntel GNU/Linux but still get the same result as last time I did. @psusi: My hdd is in GPT, so fdisk will not work. I use gdisk (AKA gpt fdisk).
    – tiger2wander
    Nov 29 '11 at 2:02












  • @UocNguyen, then whatever the equivalent for gfdisk is. The point is to verify that the partition is as large as LVM expects it to be.
    – psusi
    Nov 29 '11 at 2:17
















4














Read my story below.



I'm using LVM2 with following information:



Scan for VG:



# vgs
VG #PV #LV #SN Attr VSize VFree
unix 1 1 0 wz--n- 115.00g 45.00g


Scan for LV



# lvs
LV VG Attr LSize Origin Snap% Move Log Copy% Convert
work unix -wi-s- 70.00g


Attempt to activate VG, LV



# vgchange -ay
device-mapper: resume ioctl failed: Invalid argument
Unable to resume unix-work (254:1)
1 logical volume(s) in volume group "unix" now active


Check LV activated or not



# lvdisplay 
/dev/mapper/unix-work: open failed: No such file or directory
--- Logical volume ---
LV Name /dev/unix/work
VG Name unix
LV UUID HzzTTr-rX2d-w1dP-NEQL-QksJ-rmHW-jMTxO7
LV Write Access read/write
LV Status NOT available
LV Size 70.00 GiB
Current LE 17920
Segments 2
Allocation inherit
Read ahead sectors auto


Because of last command end with error: "/dev/mapper/unix-work: open failed: No such file or directory"
Then I have to run vgmknodes to manual create /dev/ nodes as below



# vgmknodes 
The link /dev/unix/work should had been created by udev but it was not found. Falling back to direct link creation.


Now it look like better with status "suspended"



# lvdisplay 
--- Logical volume ---
LV Name /dev/unix/work
VG Name unix
LV UUID HzzTTr-rX2d-w1dP-NEQL-QksJ-rmHW-jMTxO7
LV Write Access read/write
LV Status suspended
# open 0
LV Size 70.00 GiB
Current LE 17920
Segments 2
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:1


Attempt to mount LV:



# mount /dev/unix/work /mnt/
mount: /dev/mapper/unix-work already mounted or /mnt/ busy


Message from dmesg:



[ 1527.566964] device-mapper: table: 254:1: sda3 too small for target: start=94372224, len=136306688, dev_size=224606491


So, my question is: how can I wake up LV to mount it or use dd command to get data from LVM partition?



Thanks in advanced!










share|improve this question






















  • 1. try update the follwing packges kernel , device-mapper, lvm2 . 2. deactivate with vgchange -an , then activate with vgchange -ay.
    – Hanan N.
    Nov 28 '11 at 6:00










  • Already read on LVM FAQ but not tried yet, I'm using live cd of Arch Bang so can not make a kernel update. I think it is not related to kernel since I use live cd before & after this problem happen. FYI: uname -a Linux archbang 3.0-ARCH #1 SMP PREEMPT Wed Oct 19 10:27:51 CEST 2011 x86_64 Intel(R) Core(TM) i5-2410M CPU @ 2.30GHz GenuineIntel GNU/Linux
    – tiger2wander
    Nov 28 '11 at 8:44












  • The output from pvdisplay and fdisk -lu /dev/sda would be helpful. This part makes it sound like your partition holding the PV has shrunk, which is a big problem: sda3 too small for target: start=94372224, len=136306688, dev_size=224606491
    – psusi
    Nov 28 '11 at 15:45










  • @Hannan: I have installed Arch Linux to another partition and using latest linux kernel: Linux hydrogen 3.1.2-1-ARCH #1 SMP PREEMPT Tue Nov 22 09:17:56 CET 2011 x86_64 Intel(R) Core(TM) i5-2410M CPU @ 2.30GHz GenuineIntel GNU/Linux but still get the same result as last time I did. @psusi: My hdd is in GPT, so fdisk will not work. I use gdisk (AKA gpt fdisk).
    – tiger2wander
    Nov 29 '11 at 2:02












  • @UocNguyen, then whatever the equivalent for gfdisk is. The point is to verify that the partition is as large as LVM expects it to be.
    – psusi
    Nov 29 '11 at 2:17














4












4








4


3





Read my story below.



I'm using LVM2 with following information:



Scan for VG:



# vgs
VG #PV #LV #SN Attr VSize VFree
unix 1 1 0 wz--n- 115.00g 45.00g


Scan for LV



# lvs
LV VG Attr LSize Origin Snap% Move Log Copy% Convert
work unix -wi-s- 70.00g


Attempt to activate VG, LV



# vgchange -ay
device-mapper: resume ioctl failed: Invalid argument
Unable to resume unix-work (254:1)
1 logical volume(s) in volume group "unix" now active


Check LV activated or not



# lvdisplay 
/dev/mapper/unix-work: open failed: No such file or directory
--- Logical volume ---
LV Name /dev/unix/work
VG Name unix
LV UUID HzzTTr-rX2d-w1dP-NEQL-QksJ-rmHW-jMTxO7
LV Write Access read/write
LV Status NOT available
LV Size 70.00 GiB
Current LE 17920
Segments 2
Allocation inherit
Read ahead sectors auto


Because of last command end with error: "/dev/mapper/unix-work: open failed: No such file or directory"
Then I have to run vgmknodes to manual create /dev/ nodes as below



# vgmknodes 
The link /dev/unix/work should had been created by udev but it was not found. Falling back to direct link creation.


Now it look like better with status "suspended"



# lvdisplay 
--- Logical volume ---
LV Name /dev/unix/work
VG Name unix
LV UUID HzzTTr-rX2d-w1dP-NEQL-QksJ-rmHW-jMTxO7
LV Write Access read/write
LV Status suspended
# open 0
LV Size 70.00 GiB
Current LE 17920
Segments 2
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:1


Attempt to mount LV:



# mount /dev/unix/work /mnt/
mount: /dev/mapper/unix-work already mounted or /mnt/ busy


Message from dmesg:



[ 1527.566964] device-mapper: table: 254:1: sda3 too small for target: start=94372224, len=136306688, dev_size=224606491


So, my question is: how can I wake up LV to mount it or use dd command to get data from LVM partition?



Thanks in advanced!










share|improve this question













Read my story below.



I'm using LVM2 with following information:



Scan for VG:



# vgs
VG #PV #LV #SN Attr VSize VFree
unix 1 1 0 wz--n- 115.00g 45.00g


Scan for LV



# lvs
LV VG Attr LSize Origin Snap% Move Log Copy% Convert
work unix -wi-s- 70.00g


Attempt to activate VG, LV



# vgchange -ay
device-mapper: resume ioctl failed: Invalid argument
Unable to resume unix-work (254:1)
1 logical volume(s) in volume group "unix" now active


Check LV activated or not



# lvdisplay 
/dev/mapper/unix-work: open failed: No such file or directory
--- Logical volume ---
LV Name /dev/unix/work
VG Name unix
LV UUID HzzTTr-rX2d-w1dP-NEQL-QksJ-rmHW-jMTxO7
LV Write Access read/write
LV Status NOT available
LV Size 70.00 GiB
Current LE 17920
Segments 2
Allocation inherit
Read ahead sectors auto


Because of last command end with error: "/dev/mapper/unix-work: open failed: No such file or directory"
Then I have to run vgmknodes to manual create /dev/ nodes as below



# vgmknodes 
The link /dev/unix/work should had been created by udev but it was not found. Falling back to direct link creation.


Now it look like better with status "suspended"



# lvdisplay 
--- Logical volume ---
LV Name /dev/unix/work
VG Name unix
LV UUID HzzTTr-rX2d-w1dP-NEQL-QksJ-rmHW-jMTxO7
LV Write Access read/write
LV Status suspended
# open 0
LV Size 70.00 GiB
Current LE 17920
Segments 2
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:1


Attempt to mount LV:



# mount /dev/unix/work /mnt/
mount: /dev/mapper/unix-work already mounted or /mnt/ busy


Message from dmesg:



[ 1527.566964] device-mapper: table: 254:1: sda3 too small for target: start=94372224, len=136306688, dev_size=224606491


So, my question is: how can I wake up LV to mount it or use dd command to get data from LVM partition?



Thanks in advanced!







lvm






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 28 '11 at 2:13









tiger2wander

1281211




1281211












  • 1. try update the follwing packges kernel , device-mapper, lvm2 . 2. deactivate with vgchange -an , then activate with vgchange -ay.
    – Hanan N.
    Nov 28 '11 at 6:00










  • Already read on LVM FAQ but not tried yet, I'm using live cd of Arch Bang so can not make a kernel update. I think it is not related to kernel since I use live cd before & after this problem happen. FYI: uname -a Linux archbang 3.0-ARCH #1 SMP PREEMPT Wed Oct 19 10:27:51 CEST 2011 x86_64 Intel(R) Core(TM) i5-2410M CPU @ 2.30GHz GenuineIntel GNU/Linux
    – tiger2wander
    Nov 28 '11 at 8:44












  • The output from pvdisplay and fdisk -lu /dev/sda would be helpful. This part makes it sound like your partition holding the PV has shrunk, which is a big problem: sda3 too small for target: start=94372224, len=136306688, dev_size=224606491
    – psusi
    Nov 28 '11 at 15:45










  • @Hannan: I have installed Arch Linux to another partition and using latest linux kernel: Linux hydrogen 3.1.2-1-ARCH #1 SMP PREEMPT Tue Nov 22 09:17:56 CET 2011 x86_64 Intel(R) Core(TM) i5-2410M CPU @ 2.30GHz GenuineIntel GNU/Linux but still get the same result as last time I did. @psusi: My hdd is in GPT, so fdisk will not work. I use gdisk (AKA gpt fdisk).
    – tiger2wander
    Nov 29 '11 at 2:02












  • @UocNguyen, then whatever the equivalent for gfdisk is. The point is to verify that the partition is as large as LVM expects it to be.
    – psusi
    Nov 29 '11 at 2:17


















  • 1. try update the follwing packges kernel , device-mapper, lvm2 . 2. deactivate with vgchange -an , then activate with vgchange -ay.
    – Hanan N.
    Nov 28 '11 at 6:00










  • Already read on LVM FAQ but not tried yet, I'm using live cd of Arch Bang so can not make a kernel update. I think it is not related to kernel since I use live cd before & after this problem happen. FYI: uname -a Linux archbang 3.0-ARCH #1 SMP PREEMPT Wed Oct 19 10:27:51 CEST 2011 x86_64 Intel(R) Core(TM) i5-2410M CPU @ 2.30GHz GenuineIntel GNU/Linux
    – tiger2wander
    Nov 28 '11 at 8:44












  • The output from pvdisplay and fdisk -lu /dev/sda would be helpful. This part makes it sound like your partition holding the PV has shrunk, which is a big problem: sda3 too small for target: start=94372224, len=136306688, dev_size=224606491
    – psusi
    Nov 28 '11 at 15:45










  • @Hannan: I have installed Arch Linux to another partition and using latest linux kernel: Linux hydrogen 3.1.2-1-ARCH #1 SMP PREEMPT Tue Nov 22 09:17:56 CET 2011 x86_64 Intel(R) Core(TM) i5-2410M CPU @ 2.30GHz GenuineIntel GNU/Linux but still get the same result as last time I did. @psusi: My hdd is in GPT, so fdisk will not work. I use gdisk (AKA gpt fdisk).
    – tiger2wander
    Nov 29 '11 at 2:02












  • @UocNguyen, then whatever the equivalent for gfdisk is. The point is to verify that the partition is as large as LVM expects it to be.
    – psusi
    Nov 29 '11 at 2:17
















1. try update the follwing packges kernel , device-mapper, lvm2 . 2. deactivate with vgchange -an , then activate with vgchange -ay.
– Hanan N.
Nov 28 '11 at 6:00




1. try update the follwing packges kernel , device-mapper, lvm2 . 2. deactivate with vgchange -an , then activate with vgchange -ay.
– Hanan N.
Nov 28 '11 at 6:00












Already read on LVM FAQ but not tried yet, I'm using live cd of Arch Bang so can not make a kernel update. I think it is not related to kernel since I use live cd before & after this problem happen. FYI: uname -a Linux archbang 3.0-ARCH #1 SMP PREEMPT Wed Oct 19 10:27:51 CEST 2011 x86_64 Intel(R) Core(TM) i5-2410M CPU @ 2.30GHz GenuineIntel GNU/Linux
– tiger2wander
Nov 28 '11 at 8:44






Already read on LVM FAQ but not tried yet, I'm using live cd of Arch Bang so can not make a kernel update. I think it is not related to kernel since I use live cd before & after this problem happen. FYI: uname -a Linux archbang 3.0-ARCH #1 SMP PREEMPT Wed Oct 19 10:27:51 CEST 2011 x86_64 Intel(R) Core(TM) i5-2410M CPU @ 2.30GHz GenuineIntel GNU/Linux
– tiger2wander
Nov 28 '11 at 8:44














The output from pvdisplay and fdisk -lu /dev/sda would be helpful. This part makes it sound like your partition holding the PV has shrunk, which is a big problem: sda3 too small for target: start=94372224, len=136306688, dev_size=224606491
– psusi
Nov 28 '11 at 15:45




The output from pvdisplay and fdisk -lu /dev/sda would be helpful. This part makes it sound like your partition holding the PV has shrunk, which is a big problem: sda3 too small for target: start=94372224, len=136306688, dev_size=224606491
– psusi
Nov 28 '11 at 15:45












@Hannan: I have installed Arch Linux to another partition and using latest linux kernel: Linux hydrogen 3.1.2-1-ARCH #1 SMP PREEMPT Tue Nov 22 09:17:56 CET 2011 x86_64 Intel(R) Core(TM) i5-2410M CPU @ 2.30GHz GenuineIntel GNU/Linux but still get the same result as last time I did. @psusi: My hdd is in GPT, so fdisk will not work. I use gdisk (AKA gpt fdisk).
– tiger2wander
Nov 29 '11 at 2:02






@Hannan: I have installed Arch Linux to another partition and using latest linux kernel: Linux hydrogen 3.1.2-1-ARCH #1 SMP PREEMPT Tue Nov 22 09:17:56 CET 2011 x86_64 Intel(R) Core(TM) i5-2410M CPU @ 2.30GHz GenuineIntel GNU/Linux but still get the same result as last time I did. @psusi: My hdd is in GPT, so fdisk will not work. I use gdisk (AKA gpt fdisk).
– tiger2wander
Nov 29 '11 at 2:02














@UocNguyen, then whatever the equivalent for gfdisk is. The point is to verify that the partition is as large as LVM expects it to be.
– psusi
Nov 29 '11 at 2:17




@UocNguyen, then whatever the equivalent for gfdisk is. The point is to verify that the partition is as large as LVM expects it to be.
– psusi
Nov 29 '11 at 2:17










1 Answer
1






active

oldest

votes


















0














I think it is related to this post https://superuser.com/questions/1061454/how-to-resize-back-a-logical-volumen-lvm/1061548



As suggested by the psusi comment, the PV on /dev/sda3 seems to be smaller than the VG size (perhaps a pvresize --setphysicalvolumesize somesizeG was done at a time)



2 solutions :
- extend the /dev/sda3
- reduce the unix-work LV



But need the pvdisplay and /dev/sda3 infos






share|improve this answer





















    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "106"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f25497%2flvm2-can-not-wake-up-suspended-logical-volume%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    I think it is related to this post https://superuser.com/questions/1061454/how-to-resize-back-a-logical-volumen-lvm/1061548



    As suggested by the psusi comment, the PV on /dev/sda3 seems to be smaller than the VG size (perhaps a pvresize --setphysicalvolumesize somesizeG was done at a time)



    2 solutions :
    - extend the /dev/sda3
    - reduce the unix-work LV



    But need the pvdisplay and /dev/sda3 infos






    share|improve this answer


























      0














      I think it is related to this post https://superuser.com/questions/1061454/how-to-resize-back-a-logical-volumen-lvm/1061548



      As suggested by the psusi comment, the PV on /dev/sda3 seems to be smaller than the VG size (perhaps a pvresize --setphysicalvolumesize somesizeG was done at a time)



      2 solutions :
      - extend the /dev/sda3
      - reduce the unix-work LV



      But need the pvdisplay and /dev/sda3 infos






      share|improve this answer
























        0












        0








        0






        I think it is related to this post https://superuser.com/questions/1061454/how-to-resize-back-a-logical-volumen-lvm/1061548



        As suggested by the psusi comment, the PV on /dev/sda3 seems to be smaller than the VG size (perhaps a pvresize --setphysicalvolumesize somesizeG was done at a time)



        2 solutions :
        - extend the /dev/sda3
        - reduce the unix-work LV



        But need the pvdisplay and /dev/sda3 infos






        share|improve this answer












        I think it is related to this post https://superuser.com/questions/1061454/how-to-resize-back-a-logical-volumen-lvm/1061548



        As suggested by the psusi comment, the PV on /dev/sda3 seems to be smaller than the VG size (perhaps a pvresize --setphysicalvolumesize somesizeG was done at a time)



        2 solutions :
        - extend the /dev/sda3
        - reduce the unix-work LV



        But need the pvdisplay and /dev/sda3 infos







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Jun 26 at 15:39









        Pierre-Damien

        12




        12






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Unix & Linux Stack Exchange!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.





            Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


            Please pay close attention to the following guidance:


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f25497%2flvm2-can-not-wake-up-suspended-logical-volume%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Morgemoulin

            Scott Moir

            Souastre