[linux-lvm] vgchange doesn't activate the logical volume

[linux-lvm] vgchange doesn't activate the logical volume

[Daniel Loney]

[-- Attachment #1: Type: text/plain, Size: 2631 bytes --]

After doing random 
   vgchange -an /dev/vg02
   vgscan
   vgchange -ay /dev/vg02

vgchange no longer sets the volume to available.  The volume remains in a NOT available state.

I am using 
lvm2-2.01.14-3.6

Here is the output of the vgchange and vgdisplay commands:

suse01:~ # vgchange -vay /dev/vg02
    Using volume group(s) on command line
    Finding volume group "vg02"
  /dev/sda: read failed after 0 of 4096 at 0: Input/output error
    Activated logical volumes in volume group "vg02"
  0 logical volume(s) in volume group "vg02" now active


suse01:~ # vgdisplay -v vg02| more
    Using volume group(s) on command line
    Finding volume group "vg02"
  /dev/sda: read failed after 0 of 4096 at 0: Input/output error
  --- Volume group ---
  VG Name               vg02
  System ID
  Format                lvm2
  Metadata Areas        1
  Metadata Sequence No  18
  VG Access             read/write
  VG Status             resizable
  MAX LV                128
  Cur LV                1
  Open LV               0
  Max PV                0
  Cur PV                1
  Act PV                1
  VG Size               40.00 GB
  PE Size               4.00 MB
  Total PE              10239
  Alloc PE / Size       10000 / 39.06 GB
  Free  PE / Size       239 / 956.00 MB
  VG UUID               2XYqoQ-Ah1U-Aqc3-4beH-mZRM-o5U5-kdEDCE
    
  --- Logical volume ---
  LV Name                /dev/vg02/lvol0
  VG Name                vg02
  LV UUID                7HItNY-hmWC-AwLl-lamP-7FWq-G3Ug-irPavo
  LV Write Access        read/write
  LV Status              NOT available
  LV Size                39.06 GB
  Current LE             10000
  Segments               1
  Allocation             inherit
  Read ahead sectors     0
    
  --- Physical volumes ---
  PV Name               /dev/sdb
  PV UUID               6mxyu2-1fp0-ziRZ-VNPE-dROT-At0p-dXmFiT
  PV Status             allocatable
  Total PE / Free PE    10239 / 239



Any ideas? 
  
***************************************************************************************  
The information contained in this communication is proprietary to Israel Aircraft Industries Ltd. and/or third parties, may contain confidential or privileged information, and is intended only for the use of the intended addressee thereof. If you are not the intended addressee, please be aware that any use, disclosure, distribution and/or copying of this communication is strictly prohibited. If you receive this communication in error, please notify the sender immediately and delete it from your computer. Thank you. 

[-- Attachment #2: Type: text/html, Size: 6590 bytes --]

Re: [linux-lvm] vgchange doesn't activate the logical volume

[Patrick Caulfield]

Daniel Loney wrote:
> After doing random
>    vgchange -an /dev/vg02
>    vgscan
>    vgchange -ay /dev/vg02
>  
> vgchange no longer sets the volume to available.  The volume remains in
> a *NOT available* state.
>  
> I am using
> lvm2-2.01.14-3.6
>  
> Here is the output of the vgchange and vgdisplay commands:
>  
> suse01:~ # vgchange -vay /dev/vg02
>     Using volume group(s) on command line
>     Finding volume group "vg02"
>   /dev/sda: read failed after 0 of 4096 at 0: Input/output error


I think you need to investigate why LVM can't read /dev/sda - assuming that's
supposed to be one of your disks.

>     Activated logical volumes in volume group "vg02"
>   0 logical volume(s) in volume group "vg02" now active
>  
> suse01:~ # vgdisplay -v vg02| more
>     Using volume group(s) on command line
>     Finding volume group "vg02"
>   /dev/sda: read failed after 0 of 4096 at 0: Input/output error


-- 

patrick

Re: [linux-lvm] vgchange doesn't activate the logical volume

[Dieter Stüken]

Daniel Loney wrote:
> suse01:~ # vgdisplay -v vg02| more
>     Using volume group(s) on command line
>     Finding volume group "vg02"
>   /dev/sda: read failed after 0 of 4096 at 0: Input/output error

looks like a bad sector/read error on /dev/sda.
You may verify this either by a simple

dd if=/dev/sda of=/dev/null bs=512 iflag=direct

to find the bad sectors number. Or you may run 
"badblocks -s /dev/sda", which does roughly the same.

I strongly suggest to use smartctl to monitor the state of your
disk (see http://smartmontools.sourceforge.net). Most problems
show up here some time before your disk finally dies.

Try "smartctl -d ata -a /dev/sda" to display the disks error log.
If you did not use it before, you might have to enable it by:
"smartctl -d ata -s on /dev/sda".

All disks have spare sectors they can use, if some sector gets broken
But the sector is not automatically replaced, as most people believe.
This does not happen until some new data is written to that sector.
If your bad sector occurs within the LVM metadata description of /dev/sda
you may recover it by using "vgcfgrestore" to repair the broken LVM header.

I did not use vgcfgrestore before, so I can't describe the necessary steps
in detail. May be someone else can help here...

Dieter.

Re: [linux-lvm] vgchange doesn't activate the logical volume

[Daniel Loney]

The device in question is /dev/sdb.  At the end of the vgdisplay that I 
included you can see that the physical
volume is /dev/sdb.  sda is a volumn that doesn't exist and should be 
disregarded.  Sorry about the confusion.

Danny


----- Original Message ----- 
From: "Dieter Stüken" <stueken@conterra.de>
To: "LVM general discussion and development" <linux-lvm@redhat.com>
Sent: Wednesday, June 21, 2006 10:42 AM
Subject: Re: [linux-lvm] vgchange doesn't activate the logical volume


> Daniel Loney wrote:
>> suse01:~ # vgdisplay -v vg02| more
>>     Using volume group(s) on command line
>>     Finding volume group "vg02"
>>   /dev/sda: read failed after 0 of 4096 at 0: Input/output error
>
> looks like a bad sector/read error on /dev/sda.
> You may verify this either by a simple
>
> dd if=/dev/sda of=/dev/null bs=512 iflag=direct
>
> to find the bad sectors number. Or you may run
> "badblocks -s /dev/sda", which does roughly the same.
>
> I strongly suggest to use smartctl to monitor the state of your
> disk (see http://smartmontools.sourceforge.net). Most problems
> show up here some time before your disk finally dies.
>
> Try "smartctl -d ata -a /dev/sda" to display the disks error log.
> If you did not use it before, you might have to enable it by:
> "smartctl -d ata -s on /dev/sda".
>
> All disks have spare sectors they can use, if some sector gets broken
> But the sector is not automatically replaced, as most people believe.
> This does not happen until some new data is written to that sector.
> If your bad sector occurs within the LVM metadata description of /dev/sda
> you may recover it by using "vgcfgrestore" to repair the broken LVM 
> header.
>
> I did not use vgcfgrestore before, so I can't describe the necessary steps
> in detail. May be someone else can help here...
>
> Dieter.
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
> 
  
***************************************************************************************  
The information contained in this communication is proprietary to Israel Aircraft Industries Ltd. and/or third parties, may contain confidential or privileged information, and is intended only for the use of the intended addressee thereof. If you are not the intended addressee, please be aware that any use, disclosure, distribution and/or copying of this communication is strictly prohibited. If you receive this communication in error, please notify the sender immediately and delete it from your computer. Thank you.