Linux LVM users
 help / color / mirror / Atom feed
From: "Tim Harvey" <tharvey@alumni.calpoly.edu>
To: linux-lvm@redhat.com
Subject: [linux-lvm] Troubling activating and mounting a volume group
Date: Thu, 3 Jun 2004 00:15:30 -0700	[thread overview]
Message-ID: <000a01c4493a$8dc78310$7001a8c0@darwin> (raw)

Greetings,

I'm trying to recover data from a couple of RAID arrays that were
created in a system that has died.  The arrays themselves are intact.

I've been able to assemble the arrays and find logical volumes on them,
but I'm not sure how to activate the LG's and mount the volumes.

I've assembled the arrays with 3 out of the 4 disks, which should be
enough to access the data in a RAID1/5 array if I understand things
correctly without allowing RAID reconstruction.  Here is some data from
my progress so far:

[root@masterbackend root]# more /proc/mdstat
Personalities : [raid1] [raid5]
read_ahead 1024 sectors
md1 : active raid1 hdb2[1] hdd2[3] hdc2[2]
      513984 blocks [4/3] [_UUU]

md0 : active raid5 hdb1[1] hdd1[3] hdc1[2]
      872738880 blocks level 5, 32k chunk, algorithm 2 [4/3] [_UUU]

unused devices: <none>

md0 is a RAID5 array which has a VG called 'vgroup00' and an LV called
'storage1'.  md1 is a RAID1 array which as a VG called 'logdev'. 

[root@masterbackend root]# vgdisplay -D
--- Volume group ---
VG Name               vgroup00
VG Access             read/write
VG Status             NOT available/resizable
VG #                  0
MAX LV                256
Cur LV                1
Open LV               0
MAX LV Size           1023.97 GB
Max PV                256
Cur PV                1
Act PV                1
VG Size               832.28 GB
PE Size               16 MB
Total PE              53266
Alloc PE / Size       53266 / 832.28 GB
Free  PE / Size       0 / 0
VG UUID               oizRKm-JFUq-hMiZ-rN6F-1M7u-mRDc-vqqy1p

--- Volume group ---
VG Name               logdev
VG Access             read/write
VG Status             NOT available/resizable
VG #                  1
MAX LV                256
Cur LV                2
Open LV               0
MAX LV Size           255.99 GB
Max PV                256
Cur PV                1
Act PV                1
VG Size               1.46 GB
PE Size               4 MB
Total PE              375
Alloc PE / Size       138 / 552 MB
Free  PE / Size       237 / 948 MB
VG UUID               nCpyXh-5bn4-Qh2W-UlAc-3dyh-zQOT-i33ow8

So far I'm not understanding how to make the VG Status 'available' and
how to mount them.  I now have the following devices:

/dev/vgroup00/storage1 block special (58/2)
/dev/vgroup00/group character special (109/0)
/dev/logdev/storage1 block special (58/1) 
/dev/logdev/syslog block special (58/0) 
/dev/logdev/group character special (109/1)

I believe these are XFS but I still can't mount them via:

[root@masterbackend root]# mount /dev/vgroup00/storage1 /mnt/array/ -t
xfs
mount: wrong fs type, bad option, bad superblock on
/dev/vgroup00/storage1,
       or too many mounted file systems

Any ideas?  I'm not familiar with LVM, but have been googling it.

Thanks for any help,

Tim

             reply	other threads:[~2004-06-03  7:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-03  7:15 Tim Harvey [this message]
2004-06-03 16:40 ` [linux-lvm] Troubling activating and mounting a volume group Tim Harvey
2004-06-03 17:12   ` Tim Harvey

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='000a01c4493a$8dc78310$7001a8c0@darwin' \
    --to=tharvey@alumni.calpoly.edu \
    --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