From: Marcos Dutra <macdutra@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Volume group inconsistent
Date: Wed, 11 Feb 2015 16:35:41 -0200 [thread overview]
Message-ID: <CAPcfVV9fgo2sv+Eca3TtMeoc7LKiO=BsOf3FZFUDsLjqKYFPCA@mail.gmail.com> (raw)
In-Reply-To: <54DB66C7.5080809@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2228 bytes --]
Zdenek,
My multipath devices have an alias to plt-XX instead of the default name
mpathXX.
I can create new volumes with lvcreate, but after 3 or 4 new volumes my VG
pass to inconsistent status because 24 disks stay in missing status, I
don't know why. Do you think that the lvm cannot write properly?
My disks are provided by IBM storage DS8000 but I don't have access the
configuration. Those devices was working properly until last friday since
august 2014.
When I restore my backup with vgcfgrestore, my VG return active without
problem, then I believe I don't have problens with write properly. Do you
have any idea or a test to do? I cannot shut off this VG now because it's
active and used by virtual servers, I have a big problem now.
I created a new VG to create new volumes but I'd like fix this one.
Thanks
2015-02-11 12:27 GMT-02:00 Zdenek Kabelac <zdenek.kabelac@gmail.com>:
> Dne 9.2.2015 v 17:37 Marcos Dutra napsal(a):
>
>> Hi Zdenek,
>>
>> I attached 2 files, one with missing status and another my backup today. I
>> restored my vg from backup but I still have problem, if I create some new
>> lv
>> volumes, vg status come back with missing status, I don't know why. Since
>> saturday night I don't create any volumes in this vg and I don't have any
>> missing status until now, but I would like come back to create new lv in
>> this
>> volume.
>> My server is centos-6.6 with lastest updates.
>>
>>
>
> What are those /dev/mapper/plt-XX devices ?
>
> It seems like the lvm2 command cannot write to this place properly?
>
> Checksum error looks like serious problem.
>
> From attached output - all your PVs were properly markes as not missing,
> however the lvm2 cannot read back proper crc code.
>
> So what are those 0.5GB devices - are they properly writable ?
> (especially in the disk header)
>
> Note - there are special type of block devices like DASD devices
> that must be first properly configured by IBM storage manager to provide
> regular devices.
>
> Regards
>
>
> Zdenek
>
> _______________________________________________
> 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: 3242 bytes --]
next prev parent reply other threads:[~2015-02-11 18:35 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 [this message]
2015-02-11 23:49 ` service hofman
2015-02-12 13:57 ` Marcos Dutra
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='CAPcfVV9fgo2sv+Eca3TtMeoc7LKiO=BsOf3FZFUDsLjqKYFPCA@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).