From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Error on lvcreate or lvremove!
Date: Thu May 23 12:04:03 2002 [thread overview]
Message-ID: <20020523190023.A13788@sistina.com> (raw)
In-Reply-To: <009601c20204$81710e30$6501a8c0@bomoon>; from bo@sosnetwork.net on Wed, May 22, 2002 at 07:49:49PM -0700
On Wed, May 22, 2002 at 07:49:49PM -0700, bo wrote:
> Heinz,
>
> Thanks for your help, it worked.
> However, I do not understand why I had this problem and how your suggestion
> make
> it work. The logical volume number is managed by LVM functions.
Right.
These problems occir if volume groups are removed physically in a non-devfs
system *without* exporting them first using vgexport.
Then the /dev entries are still there.
Another example causing this is overwriting all physical volumes of a
volume group (IOW: brute force removal of a volume group).
If that happened before, creating new volume groups and/or logical volumes,
you can end up with multiple links in /dev having the same major minor numbers
causing such behaviour.
If vgexport/vgremove are used successfully instead, that shouldn't occur at all.
A 'workaround' for non-devfs configurations is
ls /dev/*/group | sed 's!/group!!' | xargs rm -r ; vgmknodes
which removes all LVM subdirectories and recreates just the valid ones
with all device specials in.
>
> Another question is
>
> I have the same problem as mentioned in "Poul Petesen's LVM1.04 pvmove is
> broken" email
> today as
> 4) The RedHat 7.2 call to vgscan in rc.sysinit happens before
> mounting other file-systems, for example "/usr". This causes the
> 1.1-rc2
> vgscan to fail since libreadline is in /usr/lib.
In order to work around this obstacle, either create the multiple
executable version by running "./configure --disable-single_exec"
(which doesn't use readline)
- or -
link the single executable statically by running
"./configure --enable-static_link" (which doesn't use the shared libs).
Regards,
Heinz -- The LVM Guy --
> I did not have this problem on LVM1.0.x. Now, I need to enable LVM and mount
> all of these volumes after system boot manually.
>
> Any suggestion or fixes?
>
> Thanks,
>
> Bo
>
> ----- Original Message -----
> From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
> To: <linux-lvm@sistina.com>
> Sent: Wednesday, May 22, 2002 5:46 AM
> Subject: Re: [linux-lvm] Error on lvcreate or lvremove!
>
>
> > On Tue, May 21, 2002 at 02:46:22PM -0700, bo wrote:
> > > Hello,
> > >
> > > I did not have this kind of problem before but I installed LVM1.1-rc2,
> > > I am experiencing the following errors;
> > >
> > > Problem1) could not create an LV from RAID1 vol group
> > > [root@localhost /]# lvcreate -l 496 -n lvraid1 volRaid1
> > > lvcreate -- ERROR "Operation not permitted" opening logical volume
> "/dev/volRaid1/lvraid1"
> >
> > Looks like your logical volume numbers are invalid.
> >
> > Take a VGDA backup with vgcfgbackup(8) and store /etc/lvmconf/*
> > in a safe location.
> >
> > Run "vgscan -f" and retry.
> >
> > >
> > > Problem2) I could not remove it
> > > [root@localhost /]# lvremove /dev/volRaid1/lvraid1
> > > lvremove -- do you really want to remove "/dev/volRaid1/lvraid1"?
> [y/n]: y
> > > lvremove -- ERROR "lv_release(): LV number" releasing logical volume
> "/dev/volRaid1/lvraid1"
> > >
> > > Problem3) I could not create a striped LV
> > > [root@localhost /]# lvcreate -l200 -i2 -I4 -n lvjb2s volDisk2
> > > lvcreate -- not enough allocatable/free physical volume space in
> "volDisk2"
> > > lvcreate -- please check, if physical volumes are allocatable
> >
> > Could be caused by the assumed logical volume number problem but please
> > check that your physical volumes are allocatable with pvdisplay(8).
> >
> > Regards,
> > Heinz -- The LVM Guy --
> >
> >
> > >
> > > Attched are more system information.
> > >
> > > Please provide me your help,
> > >
> > > Thanks,
> > >
> > > Bo
> > >
> > > [root@localhost /]# pvscan
> > > pvscan -- reading all physical volumes (this may take a while...)
> > > pvscan -- ACTIVE PV "/dev/md0" of VG "volRaid0" [1.95 GB / 1.95 GB
> free]
> > > pvscan -- ACTIVE PV "/dev/md1" of VG "volRaid0" [1.95 GB / 1.95 GB
> free]
> > > pvscan -- ACTIVE PV "/dev/md2" of VG "volRaid0" [1.95 GB / 1.95 GB
> free]
> > > pvscan -- ACTIVE PV "/dev/md3" of VG "volRaid1" [992 MB / 992 MB
> free]
> > > pvscan -- ACTIVE PV "/dev/md4" of VG "volRaid1" [992 MB / 992 MB
> free]
> > > pvscan -- ACTIVE PV "/dev/md5" of VG "volRaid5" [1.95 GB / 1.95 GB
> free]
> > > pvscan -- ACTIVE PV "/dev/md6" of VG "volRaid5" [1.95 GB / 1.95 GB
> free]
> > > pvscan -- ACTIVE PV "/dev/hdc9" of VG "volDisk" [992 MB / 992 MB
> free]
> > > pvscan -- ACTIVE PV "/dev/hdc10" of VG "volDisk2" [992 MB / 992 MB
> free]
> > > pvscan -- ACTIVE PV "/dev/hdd9" of VG "volDisk" [992 MB / 992 MB
> free]
> > > pvscan -- ACTIVE PV "/dev/hdd10" of VG "volDisk2" [992 MB / 992 MB
> free]
> > > pvscan -- ACTIVE PV "/dev/hda15" of VG "volDisk" [996 MB / 996 MB
> free]
> > > pvscan -- ACTIVE PV "/dev/hda16" of VG "volDisk2" [996 MB / 996 MB
> free]
> > > pvscan -- total: 13 [17.59 GB] / in use: 13 [17.59 GB] / in no VG: 0 [0]
> > >
> > > [root@localhost /]# vgdisplay
> > > --- Volume group ---
> > > VG Name volRaid0
> > > VG Access read/write
> > > VG Status available/resizable
> > > VG # 2
> > > MAX LV 256
> > > Cur LV 0
> > > Open LV 0
> > > MAX LV Size 255.99 GB
> > > Max PV 256
> > > Cur PV 3
> > > Act PV 3
> > > VG Size 5.84 GB
> > > PE Size 4 MB
> > > Total PE 1496
> > > Alloc PE / Size 0 / 0
> > > Free PE / Size 1496 / 5.84 GB
> > > VG UUID 89ZFBj-yaQ0-c26m-uKgF-YhvG-2lGR-C8cvWm
> > >
> > > --- Volume group ---
> > > VG Name volRaid1
> > > VG Access read/write
> > > VG Status available/resizable
> > > VG # 3
> > > MAX LV 256
> > > Cur LV 0
> > > Open LV 0
> > > MAX LV Size 255.99 GB
> > > Max PV 256
> > > Cur PV 2
> > > Act PV 2
> > > VG Size 1.94 GB
> > > PE Size 4 MB
> > > Total PE 496
> > > Alloc PE / Size 0 / 0
> > > Free PE / Size 496 / 1.94 GB
> > > VG UUID 3keDZ8-jgky-uhKS-q1bi-d1Jf-qmsq-hw7GUs
> > >
> > > --- Volume group ---
> > > VG Name volRaid5
> > > VG Access read/write
> > > VG Status available/resizable
> > > VG # 4
> > > MAX LV 256
> > > Cur LV 0
> > > Open LV 0
> > > MAX LV Size 255.99 GB
> > > Max PV 256
> > > Cur PV 2
> > > Act PV 2
> > > VG Size 3.89 GB
> > > PE Size 4 MB
> > > Total PE 996
> > > Alloc PE / Size 0 / 0
> > > Free PE / Size 996 / 3.89 GB
> > > VG UUID U2l1OW-L3ha-r3kH-BPXw-IJP5-ksA7-77iRJB
> > >
> > > --- Volume group ---
> > > VG Name volDisk
> > > VG Access read/write
> > > VG Status available/resizable
> > > VG # 0
> > > MAX LV 256
> > > Cur LV 0
> > > Open LV 0
> > > MAX LV Size 255.99 GB
> > > Max PV 256
> > > Cur PV 3
> > > Act PV 3
> > > VG Size 2.91 GB
> > > PE Size 4 MB
> > > Total PE 745
> > > Alloc PE / Size 0 / 0
> > > Free PE / Size 745 / 2.91 GB
> > > VG UUID 7RhXUS-Pw5B-EBYN-GKIM-PO1d-4uD7-4apSvp
> > >
> > > --- Volume group ---
> > > VG Name volDisk2
> > > VG Access read/write
> > > VG Status available/resizable
> > > VG # 1
> > > MAX LV 256
> > > Cur LV 0
> > > Open LV 0
> > > MAX LV Size 255.99 GB
> > > Max PV 256
> > > Cur PV 3
> > > Act PV 3
> > > VG Size 2.91 GB
> > > PE Size 4 MB
> > > Total PE 745
> > > Alloc PE / Size 0 / 0
> > > Free PE / Size 745 / 2.91 GB
> > > VG UUID VT6shD-P4lh-Rk2g-DUHi-T2ch-p14Q-kl3BuV
> > >
> > >
> > _______________________________________________
> > linux-lvm mailing list
> > linux-lvm@sistina.com
> > http://lists.sistina.com/mailman/listinfo/linux-lvm
> > read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
> >
>
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
*** Software bugs are stupid.
Nevertheless it needs not so stupid people to solve them ***
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Sistina Software Inc.
Senior Consultant/Developer Am Sonnenhang 11
56242 Marienrachdorf
Germany
Mauelshagen@Sistina.com +49 2626 141200
FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2002-05-23 12:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-21 16:48 [linux-lvm] Error on lvcreate or lvremove! bo
2002-05-22 7:50 ` Heinz J . Mauelshagen
2002-05-22 21:51 ` bo
2002-05-23 12:04 ` Heinz J . Mauelshagen [this message]
2002-05-23 22:14 ` [linux-lvm] Error on vgscan & lvremove bo
2002-05-24 4:01 ` Heinz J . Mauelshagen
2002-05-24 16:34 ` bo
2002-05-25 5:53 ` Heinz J . Mauelshagen
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=20020523190023.A13788@sistina.com \
--to=mauelshagen@sistina.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox