From: malahal@us.ibm.com
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] Major problems after soft raid 5 failure
Date: Wed, 14 Jan 2009 17:04:41 -0800 [thread overview]
Message-ID: <20090115010441.GA6852@us.ibm.com> (raw)
In-Reply-To: <496E8353.50207@gmail.com>
Colin Faber [cfaber@gmail.com] wrote:
> was unavailable. After searching around I kept coming back to suggestions
> stating that removal of the missing device from the volume group was the
> solution to getting thing back online again. So using 'vgreduce
> --removemissing raid' then 'lvchange -ay raid' to update the changes -
> Neither command errored and vgreduce noted that 'raid' was not available
> again.
Since your LV (array) is most likely allocated on md1 that disappeared,
you really want --partial (lvm command) rather than --removemissing.
Your metadata is updated and any knowledge about 'array' LV is now
almost gone due to the above 'vgreduce'. I say almost gone because it
might be there but you really need true LVM expertise now!
Did you save a copy of your old LVM metadata before the reboot? See your
/etc/lvm/backup/raid has any reference to 'array' LV at all.
--Malahal.
> So as it stands now I have no logical volume, I have a volume group and I
> have a functional md0 array. If I dump the first 50 or so megs of the md0
> raid array I can see the volume group information, as well as the lv
> information including various bits of file system information.
>
> At this point I'm wondering can I recover the logical volume and recover
> this 1.8TB of data.
>
> For completeness here is the results of various display and scan commands:
>
> root@Aria:/dev/disk/by-id# pvscan
> PV /dev/md0 VG raid lvm2 [1.82 TB / 1.82 TB free]
> Total: 1 [1.82 TB] / in use: 1 [1.82 TB] / in no VG: 0 [0 ]
>
> root@Aria:/dev/disk/by-id# pvdisplay
> --- Physical volume ---
> PV Name /dev/md0
> VG Name raid
> PV Size 1.82 TB / not usable 2.25 MB
> Allocatable yes
> PE Size (KByte) 4096
> Total PE 476933
> Free PE 476933
> Allocated PE 0
> PV UUID oI1oXp-NOSk-BJn0-ncEN-HaZr-NwSn-P9De9b
>
> root@Aria:/dev/disk/by-id# vgscan
> Reading all physical volumes. This may take a while...
> Found volume group "raid" using metadata type lvm2
>
> root@Aria:/dev/disk/by-id# vgdisplay
> --- Volume group ---
> VG Name raid
> System ID
> Format lvm2
> Metadata Areas 1
> Metadata Sequence No 11
> VG Access read/write
> VG Status resizable
> MAX LV 0
> Cur LV 0
> Open LV 0
> Max PV 0
> Cur PV 1
> Act PV 1
> VG Size 1.82 TB
> PE Size 4.00 MB
> Total PE 476933
> Alloc PE / Size 0 / 0
> Free PE / Size 476933 / 1.82 TB
> VG UUID quRohP-EcsI-iheW-lbU5-rBjO-TnqS-JbjmZA
>
> root@Aria:/dev/disk/by-id# lvscan
> root@Aria:/dev/disk/by-id#
>
> root@Aria:/dev/disk/by-id# lvdisplay
> root@Aria:/dev/disk/by-id#
>
>
> Thank you.
>
> -cf
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
next prev parent reply other threads:[~2009-01-15 1:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-15 0:29 [linux-lvm] Major problems after soft raid 5 failure Colin Faber
2009-01-15 1:04 ` malahal [this message]
2009-01-15 1:15 ` Colin Faber
2009-01-15 1:46 ` malahal
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=20090115010441.GA6852@us.ibm.com \
--to=malahal@us.ibm.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 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.