From: Zdenek Kabelac <zkabelac@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] lvcreate - device not cleared Aborting. Failed to wipe start of new LV.
Date: Tue, 23 Jun 2015 10:44:42 +0200 [thread overview]
Message-ID: <55891C7A.4070902@redhat.com> (raw)
In-Reply-To: <877fqvt03o.fsf@gmail.com>
Dne 23.6.2015 v 08:22 csanyipal@gmail.com napsal(a):
> MegaBrutal <megabrutal@gmail.com> writes:
>
>> 2015-06-21 7:49 GMT+02:00 <csanyipal@gmail.com>:
>>> # lvcreate --verbose --size 10.10G -n var bubba
>>> DEGRADED MODE. Incomplete RAID LVs will be processed.
>>
>> Hey, I just notice, your VG is in degraded mode. This is not a normal
>> condition and it can also cause unexpected things. Why is your VG
>> degraded? Does it have missing PVs?
>
> # vgdisplay -vvv
> DEGRADED MODE. Incomplete RAID LVs will be processed.
>
> Indeed.
> I don't know why is mine VG degraded.
> How can I know does it have missing PVs?
> What can I do to fix this problem?
Hi
There is nothing to fix for a user in this case.
This message is only 'informational' - probably it could be formulated
somehow differently and less 'stressful'
Also it's location is currently wrong, since it's the 'activation' could which
could recognize this case - however proper fix is not so trivial and will take
time.
So basically - this message tells you - that command operates in mode it will
process incomplete RAID LVs - and it likely should be printed only in case
there IS some raid LV....
Regards
Zdenek
next prev parent reply other threads:[~2015-06-23 8:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-19 15:02 [linux-lvm] lvcreate - device not cleared Aborting. Failed to wipe start of new LV csanyipal
2015-06-19 22:55 ` MegaBrutal
2015-06-21 5:49 ` csanyipal
2015-06-21 16:43 ` Zdenek Kabelac
2015-06-21 17:10 ` csanyipal
2015-06-23 3:48 ` MegaBrutal
2015-06-23 6:22 ` csanyipal
2015-06-23 8:44 ` Zdenek Kabelac [this message]
2015-06-19 23:09 ` Alasdair G Kergon
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=55891C7A.4070902@redhat.com \
--to=zkabelac@redhat.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).