From: G Crowe <gclvmlist@crowie.net>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Missing Logical Volumes
Date: Sat, 20 Dec 2014 10:07:38 +1100 [thread overview]
Message-ID: <5494AFBA.5010003@crowie.net> (raw)
In-Reply-To: <54945665.5060107@redhat.com>
No, this didn't work.
[root@host1 ~]# vgchange -ay array1
29 logical volume(s) in volume group "array1" now active
And the missing /dev/mapper files were not created (I left one LV
un-fixed to try any suggested solutions)
All of the other LVs in the same VG are completely usable, so it doesn't
seem to be a problem with the VG as a whole.
Thanks
GC
On 20/12/2014 3:46 AM, Jack Waterworth wrote:
> It sounds like the VG was not activated. You can activate it with the
> following command:
>
> # vgchange -ay array1
>
> Jack Waterworth, Red Hat Certified Architect
> Senior Storage Technical Support Engineer
> Red Hat Global Support Services ( 1.888.467.3342 )
>
> On 12/19/2014 05:32 AM, G Crowe wrote:
>> After rebooting, some of my logical volumes did not have device files.
>>
>> /dev/array1/LVpics
>> and
>> /dev/mapper/array1-LVpics
>> did not exist but the output of "lvdisplay" said that the volume was
>> available (see below).
>>
>> vgscan did not resolve the problem.
>>
>> I was able to regain access to the LV by renaming it, then renaming
>> it back...
>> [root@host1 ~]# lvrename /dev/array1/LVpics /dev/array1/LVpicsnew
>> Renamed "LVpics" to "LVpicsnew" in volume group "array1"
>> [root@host1 ~]# lvrename /dev/array1/LVpicsnew /dev/array1/LVpics
>> Renamed "LVpicsnew" to "LVpics" in volume group "array1"
>>
>> There are 29 LVs in the VG and 25 of them came up OK and 4 had this
>> problem. Note that there is only one single PV (a RAID6 array) in the
>> VG, and there are two VGs on the machine.
>>
>> Is this expected behaviour, or is it something I should be worried
>> about?
>>
>>
>>
>> --- Logical volume ---
>> LV Path /dev/array1/LVpics
>> LV Name LVpics
>> VG Name array1
>> LV UUID WH7g9u-Ls7J-fIpQ-Hk2p-mUuH-QRKf-9uxcM2
>> LV Write Access read/write
>> LV Creation host, time example.com, 2013-11-26 07:29:51 +1100
>> LV Status available
>> # open 0
>> LV Size 350.00 GiB
>> Current LE 89600
>> Segments 2
>> Allocation inherit
>> Read ahead sectors auto
>> - currently set to 256
>> Block device 253:9
>>
>>
>> I am running Fedora 19 with kernel 3.11.9-200.fc19.x86_64
>>
>>
>> Thanks
>>
>> GC
>>
>> _______________________________________________
>> 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/
>
> _______________________________________________
> 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/
next prev parent reply other threads:[~2014-12-19 23:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-19 10:32 [linux-lvm] Missing Logical Volumes G Crowe
2014-12-19 16:46 ` Jack Waterworth
2014-12-19 23:07 ` G Crowe [this message]
2014-12-24 13:51 ` mghofran
2015-01-02 9:16 ` Graham Crowe
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=5494AFBA.5010003@crowie.net \
--to=gclvmlist@crowie.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.