linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: "Argus Array" <argusarray2@gmail.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] Re: newbie problem with LVM
Date: Fri, 23 Jun 2006 02:54:15 -0400	[thread overview]
Message-ID: <9fcb471e0606222354i6460bd02jf75fac7caebb3f2b@mail.gmail.com> (raw)
In-Reply-To: <9fcb471e0606222346yf25f198ve73e877d24db257c@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2469 bytes --]

Terribly sorry for the double post to the mailing list, accidentally hit the
google shortcut.

I have been using LVM for several months to record video files for my PVR
across a 200GB and 160GB disk (hdb and hdc).

Recently I decided to upgrade my FC3 install to FC5.  After the install, my
LVM mount does not come up.  It appeared that all of the LVM information in
/dev/ was gone; however, only the non-LVM drive (/dev/hda) should have been
touched by the FC5 upgrade.

This is my fstab entry:
/dev/VGforMythTV/video  /var/media              xfs     defaults        1 1

This is what fdisk shows:
/dev/hdb1               1       24792   199141708+  8e  Linux LVM

/dev/hdc1               1       19929   160079661   8e  Linux LVM

In my attempt to fix this, I think I may have totally fouled things up; I
tried to create a new volume group with the same name and more PVs for the
new drives, then combine them together into an PV with the old LV name.
However, this still does not allow it to mount.

Any ideas?  Have I deleted all my data?

Thanks for any help,

Argus

I've pasted my history commands below.

  548  more /etc/fstab
  549  vgcreate VGforMythTV -s 64m /dev/hda1
  550  /usr/sbin/vgcreate VGforMythTV -s 64m /dev/hda1
  551*
  552  /usr/sbin/pvcreate /dev/hdb1
  553  /usr/sbin/pvcreate /dev/hdc1
  554  /usr/sbin/vgcreate VGforMythTV /dev/hdb1 /dev/hdc1
  555  mount /dev/VGforMythTV /var/media
  556  mount /dev/VGforMythTV/video /var/media
  557  mount /dev/VGforMythTV/media /var/media
  558  lvcreate --name video VGforMythTV
  559  /usr/sbin/lvcreate --name video VGforMythTV
  560  /usr/sbin/lvcreate --name video -l VGforMythTV
  561  /usr/sbin/lvcreate --name video -l ` VGforMythTV
  562  /usr/sbin/lvcreate --name video -l 1 VGforMythTV
  563  mount /dev/VGforMythTV/media /var/media
  564  mount /dev/VGforMythTV/video /var/media
  565  mount -t xfs /dev/VGforMythTV/video /var/media
  566  mount /dev/VGforMythTV/video /var/media
  567  /usr/sbin/lvcreate --name video -l 2 VGforMythTV
  568  ls
  569  /usr/sbin/pvdisplay
  570  /usr/sbin/lvmdiskscan
  571  mount /dev/VGforMythTV /var/media/
  572  mount /dev/VGforMythTV/video /var/media/
  573  mount /dev/VGforMythTV/media /var/media/
  574  mount /dev/VGforMythTV/video /var/media/
  575  /sbin/fdisk /dev/hdb
  576  /sbin/fdisk /dev/hdc
  577  /usr/sbin/vgextend
  578  more /etc/fstab
  579  /usr/sbin/vgextend VGforMythTV /dev/hdb1
  580  /usr/sbin/vgextend VGforMythTV /dev/hdb

[-- Attachment #2: Type: text/html, Size: 3382 bytes --]

  reply	other threads:[~2006-06-23  6:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-23  6:46 [linux-lvm] newbie problem with LVM Argus Array
2006-06-23  6:54 ` Argus Array [this message]
2006-06-26  2:32   ` [linux-lvm] " Argus Array

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=9fcb471e0606222354i6460bd02jf75fac7caebb3f2b@mail.gmail.com \
    --to=argusarray2@gmail.com \
    --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).