From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mx1.redhat.com (ext-mx13.extmail.prod.ext.phx2.redhat.com [10.5.110.18]) by int-mx13.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id t1CDvEtj002311 for ; Thu, 12 Feb 2015 08:57:14 -0500 Received: from mail-ob0-f180.google.com (mail-ob0-f180.google.com [209.85.214.180]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id t1CDvCEQ001919 (version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=FAIL) for ; Thu, 12 Feb 2015 08:57:13 -0500 Received: by mail-ob0-f180.google.com with SMTP id vb8so9955921obc.11 for ; Thu, 12 Feb 2015 05:57:12 -0800 (PST) MIME-Version: 1.0 In-Reply-To: References: <54D87F38.4010303@redhat.com> <54DB66C7.5080809@gmail.com> Date: Thu, 12 Feb 2015 11:57:12 -0200 Message-ID: From: Marcos Dutra Content-Type: multipart/alternative; boundary=047d7b4725ee2b4364050ee47fba Subject: Re: [linux-lvm] Volume group inconsistent Reply-To: LVM general discussion and development List-Id: LVM general discussion and development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , List-Id: To: LVM general discussion and development --047d7b4725ee2b4364050ee47fba Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Thanks again Eric! You're wright, I have 64 pv each one 500GB hdd. I have problems with my pv starting by pv0 until pv23, I had seen after dd lvm doesn't recognize the devices of these pvs, status "unknown device", others devices I don't have the same problem. I cut this output from dd of hdisk plt-85 =3D pv64 Device with problem ----- pv0 { id =3D "N7lOu9-Ahjn-lf19-WVFW-xglN-yfL6-KOOw6O" device =3D "unknown device" status =3D ["ALLOCATABLE"] flags =3D ["MISSING"] dev_size =3D 1048576000 pe_start =3D 2048 pe_count =3D 127999 } ----- Device without problem ----- pv24 { id =3D "D8aEQf-2CVS-oyVE-t40G-kOd7-eUe5-SkCe8V" device =3D "/dev/mapper/mpathr" status =3D ["ALLOCATABLE"] flags =3D [] dev_size =3D 1048576000 pe_start =3D 2048 pe_count =3D 127999 } ----- But the output from another hdisk plt-01 =3D pv0 I have different view. ----- pv0 { id =3D "N7lOu9-Ahjn-lf19-WVFW-xglN-yfL6-KOOw6O" device =3D "/dev/mapper/plt-01" status =3D ["ALLOCATABLE"] flags =3D ["MISSING"] dev_size =3D 1048576000 pe_start =3D 2048 pe_count =3D 127999 } ----- I'm getting crazy lol... Thank you Marcos Dutra 2015-02-11 21:49 GMT-02:00 service hofman : > ---- > pv64 { > id =3D "TFSqaf-Wd6b-9w2r-8ZLp-rVN9-5851-0qNX0z" > device =3D "/dev/mapper/plt-85" # Hint only > > status =3D ["ALLOCATABLE"] > flags =3D [] > dev_size =3D 1048576000 # 500 Gigabytes > pe_start =3D 2048 > pe_count =3D 127999 # 499.996 Gigabytes > } > } > > ---- > > pvXX this is One for Team or for [hdd] /dev/sdX > this look like you have 64hdd for 500Gb one. > > and first look MBR 0-2Mb > > dd if=3D/dev/sdX of=3D/boot/sdX.mbr bs=3D512 count=3D4000 > > in side sdX.mbr is lvm.vg > if is this same [ platinum_after_missing.vg ] > > you found all record /etc/lvm/* > > rest is easy. > > device is inode, but not lv. > [ -b "/dev/mapper/plt-01" ] && echo "True " || echo "False" > > ----- > > logical_volumes { > > volume-a2d55040-a597-419b-95b6-403f5b287773 { > id =3D "GA9jj9-hooD-Au8T-23Bw-LNox-LkWF-G1TUG6" > status =3D ["READ", "WRITE", "VISIBLE"] > flags =3D [] > creation_host =3D "brasilia" > creation_time =3D 1409946331 # 2014-09-05 > 16:45:31 -0300 > segment_count =3D 1 > > > > segment1 { > start_extent =3D 0 > extent_count =3D 1024 # 4 Gigabytes > > type =3D "striped" > stripe_count =3D 1 # linear > > stripes =3D [ > > "pv10", 30730 > ] > } > } > > ----- > segment1 =3D=3D lv like /dev/sdX1 > > pv10=3D=3D[hdd X], offset[sdX1] =3D=3D [ -->[xxx] ] > but every one is start =3D=3D 0[+offset] > 30730*4096=3D[offset] > > > by recovery us dd if=3D/dev/sdX1 bs=3D4096 count=3D(1024*1000) seek=3D($o= ffset) > > > this not LVM only IBM LLVM > LINUX use LVM. kernel.org > IBM use AIX kernel > > > > ComputerAlarmTechnologySystem=C2=A9 > > http://plus.google.com/105013137826111836446 > +44 77 04 24 74 00 > > _______________________________________________ > 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/ > --047d7b4725ee2b4364050ee47fba Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Thanks again Eric!

You're wright, I= have 64 pv each one 500GB hdd. I have problems with my pv starting by pv0 = until pv23, I had seen after dd lvm doesn't recognize the devices of th= ese pvs, status "unknown device", others devices I don't have= the same problem. I cut this output from dd of hdisk plt-85 =3D pv64
=

Device with problem

-----

pv0 {
id =3D "N7lOu9-Ahjn-lf19-WVF= W-xglN-yfL6-KOOw6O"
device =3D "unknown device"

status =3D ["ALLOCATABLE"]
flags= =3D ["MISSING"]
dev_size =3D 1048576000
pe_s= tart =3D 2048
pe_count =3D 127999
}
-----

Device without problem

-----

pv24 {
id =3D= "D8aEQf-2CVS-oyVE-t40G-kOd7-eUe5-SkCe8V"
device =3D &q= uot;/dev/mapper/mpathr"

status =3D ["ALL= OCATABLE"]
flags =3D []
dev_size =3D 1048576000
pe_start =3D 2048
pe_count =3D 127999
}

-----


But t= he output from another hdisk plt-01 =3D pv0 I have different view.

-----

pv0 {
id =3D= "N7lOu9-Ahjn-lf19-WVFW-xglN-yfL6-KOOw6O"
device =3D &q= uot;/dev/mapper/plt-01"

status =3D ["ALL= OCATABLE"]
flags =3D ["MISSING"]
dev_siz= e =3D 1048576000
pe_start =3D 2048
pe_count =3D 127999<= /div>
}

-----

I= 'm getting crazy lol...

Thank you
Marcos Dutra


2015-02-11 21:49 GMT-02:00 service hofma= n <service.hofman@googlemail.com>:
----
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 pv64 {
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 id =3D "TFSqaf-Wd6b-9w2r-8ZLp-rVN9-5851-0qNX0z"
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 device =3D "/dev/mapper/plt-85"=C2=A0 =C2=A0# Hint onl= y

=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 status =3D ["ALLOCATABLE"]
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 flags =3D []
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 dev_size =3D 1048576000=C2=A0 =C2=A0# 500 Gigabytes
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 pe_start =3D 2048
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 pe_count =3D 127999=C2=A0 =C2=A0 =C2=A0 =C2=A0# 499.996 Gigabyte= s
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 }
=C2=A0 =C2=A0 =C2=A0 =C2=A0 }

----

pvXX this is One for Team or for [hdd] /dev/sdX
this look like you have 64hdd for 500Gb one.

and first look MBR 0-2Mb

dd if=3D/dev/sdX of=3D/boot/sdX.mbr bs=3D512 count=3D4000

in side=C2=A0 sdX.mbr is lvm.vg=
if is this same [ platinum_after_missing.vg ]

you found all record /etc/lvm/*

rest is easy.

device is inode, but not lv.
[ -b "/dev/mapper/plt-01" ] && echo "True " || = echo "False"

-----

=C2=A0 =C2=A0 =C2=A0 =C2=A0 logical_volumes {

=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 volume-a2d55040-a59= 7-419b-95b6-403f5b287773 {
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 id =3D "GA9jj9-hooD-Au8T-23Bw-LNox-LkWF-G1TUG6"
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 status =3D ["READ", "WRITE", "VISIBLE&q= uot;]
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 flags =3D []
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 creation_host =3D "brasilia"
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 creation_time =3D 1409946331=C2=A0 =C2=A0 =C2=A0 # 2014-09-05 16= :45:31 -0300
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 segment_count =3D 1



=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 segment1 {
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 start_extent =3D 0
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 extent_count =3D 1024=C2=A0 =C2=A0 = =C2=A0# 4 Gigabytes

=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 type =3D "striped"
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 stripe_count =3D 1=C2=A0 =C2=A0 =C2= =A0 =C2=A0 # linear

=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 stripes =3D [

=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 "pv= 10", 30730
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ]
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 }
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 }

-----
segment1 =3D=3D lv like /dev/sdX1

pv10=3D=3D[hdd X],=C2=A0 offset[sdX1] =3D=3D [=C2=A0 -->[xxx] ]
but every one is start =3D=3D 0[+offset]
30730*4096=3D[offset]


by recovery us dd if=3D/dev/sdX1 bs=3D4096 count=3D(1024*1000) seek=3D($off= set)


this not LVM only IBM LLVM
LINUX use LVM. kernel.org
IBM use AIX kernel



ComputerAlarmTechnologySystem=C2=A9

= http://plus.google.com/105013137826111836446
+44 = 77 04 24 74 00

____________________________= ___________________
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/

--047d7b4725ee2b4364050ee47fba--