From: Marcos Dutra <macdutra@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Volume group inconsistent
Date: Thu, 12 Feb 2015 11:57:12 -0200 [thread overview]
Message-ID: <CAPcfVV9zMKV2+UF-Y6WFr-TcSPeWpBeta+y-cTSaHCaFPL9E6Q@mail.gmail.com> (raw)
In-Reply-To: <CAKPhfZOb+NS5MD6AvAD8ySa4F6JM5_P-3+utMDva8THyfFVZGA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3773 bytes --]
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 = pv64
Device with problem
-----
pv0 {
id = "N7lOu9-Ahjn-lf19-WVFW-xglN-yfL6-KOOw6O"
device = "unknown device"
status = ["ALLOCATABLE"]
flags = ["MISSING"]
dev_size = 1048576000
pe_start = 2048
pe_count = 127999
}
-----
Device without problem
-----
pv24 {
id = "D8aEQf-2CVS-oyVE-t40G-kOd7-eUe5-SkCe8V"
device = "/dev/mapper/mpathr"
status = ["ALLOCATABLE"]
flags = []
dev_size = 1048576000
pe_start = 2048
pe_count = 127999
}
-----
But the output from another hdisk plt-01 = pv0 I have different view.
-----
pv0 {
id = "N7lOu9-Ahjn-lf19-WVFW-xglN-yfL6-KOOw6O"
device = "/dev/mapper/plt-01"
status = ["ALLOCATABLE"]
flags = ["MISSING"]
dev_size = 1048576000
pe_start = 2048
pe_count = 127999
}
-----
I'm getting crazy lol...
Thank you
Marcos Dutra
2015-02-11 21:49 GMT-02:00 service hofman <service.hofman@googlemail.com>:
> ----
> pv64 {
> id = "TFSqaf-Wd6b-9w2r-8ZLp-rVN9-5851-0qNX0z"
> device = "/dev/mapper/plt-85" # Hint only
>
> status = ["ALLOCATABLE"]
> flags = []
> dev_size = 1048576000 # 500 Gigabytes
> pe_start = 2048
> pe_count = 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=/dev/sdX of=/boot/sdX.mbr bs=512 count=4000
>
> 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 = "GA9jj9-hooD-Au8T-23Bw-LNox-LkWF-G1TUG6"
> status = ["READ", "WRITE", "VISIBLE"]
> flags = []
> creation_host = "brasilia"
> creation_time = 1409946331 # 2014-09-05
> 16:45:31 -0300
> segment_count = 1
>
>
>
> segment1 {
> start_extent = 0
> extent_count = 1024 # 4 Gigabytes
>
> type = "striped"
> stripe_count = 1 # linear
>
> stripes = [
>
> "pv10", 30730
> ]
> }
> }
>
> -----
> segment1 == lv like /dev/sdX1
>
> pv10==[hdd X], offset[sdX1] == [ -->[xxx] ]
> but every one is start == 0[+offset]
> 30730*4096=[offset]
>
>
> by recovery us dd if=/dev/sdX1 bs=4096 count=(1024*1000) seek=($offset)
>
>
> this not LVM only IBM LLVM
> LINUX use LVM. kernel.org
> IBM use AIX kernel
>
>
>
> ComputerAlarmTechnologySystem©
>
> 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/
>
[-- Attachment #2: Type: text/html, Size: 6126 bytes --]
next prev parent reply other threads:[~2015-02-12 13:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-07 15:47 [linux-lvm] Volume group inconsistent Marcos Dutra
2015-02-09 9:34 ` Zdenek Kabelac
2015-02-09 16:37 ` Marcos Dutra
2015-02-11 11:17 ` service hofman
2015-02-11 11:19 ` service hofman
2015-02-11 21:45 ` Marcos Dutra
2015-02-11 14:27 ` Zdenek Kabelac
2015-02-11 18:35 ` Marcos Dutra
2015-02-11 23:49 ` service hofman
2015-02-12 13:57 ` Marcos Dutra [this message]
2015-02-13 20:37 ` service hofman
2015-02-23 18:00 ` Marcos Dutra
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAPcfVV9zMKV2+UF-Y6WFr-TcSPeWpBeta+y-cTSaHCaFPL9E6Q@mail.gmail.com \
--to=macdutra@gmail.com \
--cc=linux-lvm@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).