All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Cowling <andy@redeye.com>
To: linux-lvm@sistina.com
Subject: [linux-lvm] the curious case of the semi-created Logical Volume
Date: 07 Feb 2001 15:30:45 +0000	[thread overview]
Message-ID: <m21ytase6y.fsf_-_@andy.off.redeye.com> (raw)
In-Reply-To: Patrick Caulfield's message of "Wed, 7 Feb 2001 14:28:18 +0000"

SuSE 7.0 with 4 x 8Gb SCSI disks. All filesystems are ext2.

I have created PV's, VG's and 2 LV's each of 8Gb and created ext2
filesystems on them and mounted them successfully.

Now I want to extend 'lv02' to 16Gb but lvextend claims the LV is not
active. Similarly lvdisplay only lists the LV using '-d'.

I created this setup using Yast (not the command-line).

Is there any way to retrieve the situation ? I am not at all familiar
with LVM configuration files and this is a live system   :-(

Thanks, as always, for any help.
-- 
Andy Cowling
RedEye International

#  lvextend -L +3920M  /dev/pv01/lv01 /dev/sdb1
lvextend -- logical volume "/dev/pv01/lv01" isn't active
#  lvscan
lvscan -- ACTIVE   "/dev/pv02/lv02" [7.81 GB]
lvscan -- ACTIVE   "/dev/pv01/lv01" [7.84 GB]
lvscan -- 2 logical volumes with 15.65 GB total in 2 volume groups
lvscan -- 2 active logical volumes
#  vgscan
vgscan -- reading all physical volumes (this may take a while...)
vgscan -- found active volume group "pv01"
vgscan -- found active volume group "pv02"
vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d" successfully created
vgscan -- WARNING: you may not have an actual backup of your volume groups
#  pvscan
pvscan -- reading all physical volumes (this may take a while...)
pvscan -- inactive PV "/dev/sdb1" of VG "pv01" [3.83 GB / 3.83 GB free]
pvscan -- inactive PV "/dev/sdb2" of VG "pv01" [3.83 GB / 0 free]
pvscan -- inactive PV "/dev/sdc2" of VG "pv02" [4.39 GB / 0 free]
pvscan -- inactive PV "/dev/sdc3" of VG "pv01" [4.01 GB / 0 free]
pvscan -- inactive PV "/dev/sdd2" of VG "pv02" [4.39 GB / 1000 MB free]
pvscan -- inactive PV "/dev/sdd3" of VG "pv01" [4.01 GB / 4.01 GB free]
pvscan -- total: 6 [24.48 GB] / in use: 6 [24.48 GB] / in no VG: 0 [0]
#  lvdisplay /dev/pv01/lv01
lvdisplay -- logical volume "/dev/pv01/lv01" is not active; try -D
#  lvdisplay -D /dev/pv01/lv01
--- Logical volume ---
LV Name               /dev/pv01/lv01
VG Name               pv01
LV Write Access       read/write
LV Status             available
LV #                  1
# open                0
LV Size               7.84 GB
Current LE            2007
Allocated LE          2007
Allocation            next free
Read ahead sectors    128
Block device          58:0

             reply	other threads:[~2001-02-07 15:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-07 15:30 Andy Cowling [this message]
2001-02-08  9:31 ` [linux-lvm] the curious case of the semi-created Logical Volume Patrick Caulfield
2001-02-08  9:44   ` Andy Cowling
2001-02-08 10:06     ` Patrick Caulfield
2001-02-08 10:45       ` Andy Cowling
2001-02-08 14:36         ` Patrick Caulfield
2001-02-08 15:29           ` Andy Cowling
2001-02-08 19:19             ` Andreas Dilger

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=m21ytase6y.fsf_-_@andy.off.redeye.com \
    --to=andy@redeye.com \
    --cc=linux-lvm@sistina.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.