All of lore.kernel.org
 help / color / mirror / Atom feed
From: Magnus Runesson <mr-lvm@linuxalert.org>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] volume group not found????
Date: Wed, 01 Aug 2001 20:39:13 +0200	[thread overview]
Message-ID: <3B684CD1.1050209@linuxalert.org> (raw)
In-Reply-To: 00ac01c11a7f$9fac1bf0$0df1d981@piefke

It looks like you have hit the bug 193 in bugzilla.

/Magnus

Alexander Bruns wrote:

> Hi,
> 
> I am new to this group an new to lvm. I reinstalled my personal server
> with redhat 7.1 an wanted to get lvm run over my three large discs.
> 
> I had the following things running for a short while:
> 
> - RedHat 7.1 with all updates.
> - self-compiled Kernel 2.4.6 with patched lvm 0.9.1_beta7
> 
> On my first HD Igave the rest space to hda7 with fdisk and set the
> partition to "8e" lvm.
> 
> The i followed the howto at sistina at:
> file://sistina.com/lvm/doc/lvm_howto/Common_tasks.html
> 
> 
> - I initalized the Partition:
>   pvcreate /dev/hda7
> 
> - I added the partition to a new volume group:
>   vgcreate lvm_volume_01 /dev(hda7
> 
> - then o activated the volume group:
>   vgchange -a y lvm_volume_01
> 
> - The I put a logical volume on the volume group:
>   lvcrate -L50G -nlvm_lv_01 lvm_volume_01
> 
> This logical Volume was then at /dev/lvm_volume_01/lvm_lv_01 and o
> formated it woith reiserfs an mounted it! Evething runs fine.
> 
> I copied the old contents of hdb5 and hdc5 of the smaller HDs to this
> logical volume. on hda7.
> 
> 
> 
> Then I added deleted the partition on hdc5, made a new one, set it to
> 8e an added it to the volume group as explained at:
> file://sistina.com/lvm/doc/lvm_howto/Common_tasks.html
> 
> 
> pvcreate /dev/hdc5
> vgextend lvm_volume_01
> lvextend -L30G /dev/lvm_volume_01/lvm_lv_01
> resize_reiserfs -f /dev/lvm_volume_01/lvm_lv_01
> 
> That was all fine and i could mount the lvm_lv_01 without any
> problems.
> 
> 
> The same I then wanted to manage with the thirt HD at hdb5, but then
> something went wrong??
> 
> Resize reiserfs did something but when i wanted to mount the LV it did
> not work. reiserfs-checks did not found a problem but the mount-binary
> told my something about a superblock......
> 
> 
> Abter a reboot I now have the following:
> 
> [root@holodeck lvmconf]# pvdisplay /dev/hda7
> pvdisplay
> --- Physical volume ---
> PV Name               /dev/hda7
> VG Name               lvm_volume_01
> PV Size               48.54 GB / NOT usable 1.06 MB [LVM: 169 KB]
> PV#                   1
> PV Status             available
> Allocatable           yes (but full)
> Cur LV                1
> PE Size (KByte)       4096
> Total PE              12425
> Free PE               0
> Allocated PE          12425
> PV UUID               cFFBJX-aqxr-P7kU-71OY-pgpX-rvtA-XxVpoc
> 
> But for /dev/hdb5 and /ev/hdc5 it does not show the same. NOTHING!!
> 
> 
> 
> And becouse I did not write anything to the volumegroup or logical
> volume after the added two partition al my data must still be on hda7.
> But how do I manage to get on it?
> 
> The following commands say the folling:
> #####################################################
> 
> 
> 
> [root@holodeck lvmconf]# vgscan
> vgscan
> vgscan -- reading all physical volumes (this may take a while...)
> vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d" successfully created
> vgscan -- WARNING: This program does not do a VGDA backup of your
> volume group
> 
> lvm_volume_01 is not found
> 
> [root@holodeck lvmconf]# vgchange -a y lvm_volume_01
> vgchange
> vgchange -- volume group "lvm_volume_01" does not exist
> 
> 
> 
> [root@holodeck lvmconf]# ls -al /dev/lvm*
> crw-r-----    1 root     root     109,   0 Jul 20 16:39 /dev/lvm
> 
> /dev/lvm_volume_01:
> insgesamt 88
> dr-xr-xr-x    2 root     root         4096 Jul 20 23:06 .
> drwxr-xr-x   15 root     root        81920 Jul 28 13:12 ..
> crw-r-----    1 root     disk     109,   0 Jul 20 23:02 group
> brw-rw----    1 root     disk      58,   0 Jul 20 23:06 lvm_lv_01
> 
> 
> [root@holodeck lvmconf]# ls -al /dev/lvm_volume_01/
> insgesamt 88
> dr-xr-xr-x    2 root     root         4096 Jul 20 23:06 .
> drwxr-xr-x   15 root     root        81920 Jul 28 13:12 ..
> crw-r-----    1 root     disk     109,   0 Jul 20 23:02 group
> brw-rw----    1 root     disk      58,   0 Jul 20 23:06 lvm_lv_01
> 
> 
> 
> 
> SHIT!
> 
> How do I get on my Data at lvm_volume_01 bzw lvm_lv_01.
> lvm_lv_01 was formated with reiserfs
> 
> 
> 
> Greetings from Germany from Alex
> 
> _______________________________________________
> 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
> 
> 

  reply	other threads:[~2001-08-01 18:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-01 11:46 [linux-lvm] volume group not found???? Alexander Bruns
2001-08-01 18:39 ` Magnus Runesson [this message]
2001-08-13  1:26   ` Alexander Bruns
2001-08-13  1:42     ` Christopher Blunck
  -- strict thread matches above, loose matches on Subject: below --
2001-09-21  3:06 tim
2001-09-21  3:58 [linux-lvm] Volume " tim
2001-09-24 11:18 ` 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=3B684CD1.1050209@linuxalert.org \
    --to=mr-lvm@linuxalert.org \
    --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.