linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: G Crowe <gclvmlist@crowie.net>
To: linux-lvm@redhat.com
Subject: [linux-lvm] Missing Logical Volumes
Date: Fri, 19 Dec 2014 21:32:25 +1100	[thread overview]
Message-ID: <5493FEB9.7010009@crowie.net> (raw)

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

             reply	other threads:[~2014-12-19 10:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-19 10:32 G Crowe [this message]
2014-12-19 16:46 ` [linux-lvm] Missing Logical Volumes Jack Waterworth
2014-12-19 23:07   ` G Crowe
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=5493FEB9.7010009@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 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).