All of lore.kernel.org
 help / color / mirror / Atom feed
From: Faux Pas III <fauxpas@trellisinc.com>
To: linux-lvm@sistina.com
Subject: [linux-lvm] Problem using lvreduce
Date: Wed, 15 Aug 2001 19:50:08 -0400	[thread overview]
Message-ID: <20010815195008.A9648@trellisinc.com> (raw)

I have been having a problem removing a drive from a running 
volume group.  I repeat this by creating a volume group from
/dev/sda, /dev/sdb (each 18gb), /dev/hde, and /dev/hdg (each
30gb).  I create an LV that spans all physical extents in 
this group.  I then try to use lvreduce to take 4400 PE's out
of the group (slightly more than occupy either of the two 
scsi drives).

Gryphon:~# lvreduce -l -4400 /dev/test_vg/test_lv 
lvreduce -- WARNING: reducing active logical volume to 72.62 GB
lvreduce -- THIS MAY DESTROY YOUR DATA (filesystem etc.)
lvreduce -- do you really want to reduce "/dev/test_vg/test_lv"? [y/n]: y
lvreduce -- ERROR "pv_check_consistency_all_pv(): PE" volume group "test_vg" is inconsistent
lvreduce -- WARNING: you don't have an automatic backup of "test_vg"
lvreduce -- logical volume "/dev/test_vg/test_lv" successfully reduced

After this, all manner of badness ensues, including:

Gryphon:~# vgdisplay
vgdisplay -- ERROR: VGDA in kernel and lvmtab are NOT consistent; please run vgscan

In any event, I'm not able to pvmove or vgreduce to get the drive out of
the volume group as I would expect.   This is on 2.4.8 + LVM 1.0, and also
manifests on 2.4.7 + LVM 0.9.1beta8.  I can provide any other diagnostic
info that would be helpful, as I can reproduce this problem easily.

-- 
Josh Litherland (fauxpas@trellisinc.com)
 It is by caffeine alone that I set my mind in motion.
  It is by the juice of Mtn Dew that thoughts acquire speed.

             reply	other threads:[~2001-08-15 23:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-15 23:50 Faux Pas III [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-08-16 17:06 [linux-lvm] Problem using lvreduce Soohoon Lee
2001-08-16 20:19 ` Faux Pas III
2001-08-17 10:43 ` Joe Thornber
2001-08-17 13:05   ` Goetz Bock
2001-08-17 13:14     ` Joe Thornber
2001-08-17 14:38   ` Heinz J . Mauelshagen
2001-08-17 15:41     ` Faux Pas III
2001-08-18 10:04       ` Joe Thornber
2001-08-20  4:05         ` Faux Pas III
2001-08-17 15:33 Soohoon Lee

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=20010815195008.A9648@trellisinc.com \
    --to=fauxpas@trellisinc.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.