From: Mark Krenz <mark@suso.org>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] HDD Failure
Date: Mon, 18 Sep 2006 19:37:28 +0000 [thread overview]
Message-ID: <20060918193728.GC28043@arvo.suso.org> (raw)
In-Reply-To: <1158608077.7182.18.camel@localhost.localdomain>
Nick,
LVM != RAID
You should have been doing RAID if you wanted to be able to handle the
failure of one drive.
On Mon, Sep 18, 2006 at 07:34:37PM GMT, Nick [lists@mogmail.net] said the following:
> Hi Fabien,
>
> Yes, just one LV - "Vol1-share".
>
> Does this mean I've lost *everything*? I would have though I should be
> still be able to access everything on the two working disks?
>
> I don't have a backup of this data.
>
> Thanks, Nick
>
> root@nibiru:~# pvdisplay
> --- Physical volume ---
> PV Name /dev/hda4
> VG Name Vol1
> PV Size 106.79 GB / not usable 0
> Allocatable yes
> PE Size (KByte) 4096
> Total PE 27339
> Free PE 27339
> Allocated PE 0
> PV UUID Cq9xKF-W33m-BCLt-YyIc-EEfm-Btqc-eZLHNh
>
> --- Physical volume ---
> PV Name /dev/hdb1
> VG Name Vol1
> PV Size 111.75 GB / not usable 0
> Allocatable yes
> PE Size (KByte) 4096
> Total PE 28609
> Free PE 28609
> Allocated PE 0
> PV UUID hwQrhH-iXHO-Bots-6zUQ-w8JG-Nmb3-shqZiX
>
> root@nibiru:~# vgdisplay
> --- Volume group ---
> VG Name Vol1
> System ID
> Format lvm2
> Metadata Areas 2
> Metadata Sequence No 3
> VG Access read/write
> VG Status resizable
> MAX LV 0
> Cur LV 0
> Open LV 0
> Max PV 0
> Cur PV 2
> Act PV 2
> VG Size 218.55 GB
> PE Size 4.00 MB
> Total PE 55948
> Alloc PE / Size 0 / 0
> Free PE / Size 55948 / 218.55 GB
> VG UUID RORj4f-LAOJ-83YS-34lD-4YRM-FKP8-8hgXLg
>
>
> On Mon, 2006-09-18 at 21:23 +0200, Fabien Jakimowicz wrote:
> > did you have only one lv in your vg ?
> >
> > if yes, you can go to your backups.
> >
> > what does pvdisplay and vgdisplay says ?
> > _______________________________________________
> > 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/
>
> _______________________________________________
> 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/
--
Mark S. Krenz
IT Director
Suso Technology Services, Inc.
http://suso.org/
next prev parent reply other threads:[~2006-09-18 19:37 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-18 18:10 [linux-lvm] HDD Failure Nick
2006-09-18 19:08 ` Mitch Miller
2006-09-18 19:13 ` Nick
2006-09-18 19:23 ` Fabien Jakimowicz
2006-09-18 19:34 ` Nick
2006-09-18 19:37 ` Mark Krenz [this message]
2006-09-19 22:40 ` [linux-lvm] Misleading documentation (was: HDD Failure) Scott Lamb
2006-09-20 0:35 ` Fabien Jakimowicz
2006-09-20 3:22 ` Mark Krenz
2006-09-20 11:27 ` Fabien Jakimowicz
2006-09-20 19:45 ` [linux-lvm] Misleading documentation Barnaby Claydon
2006-09-20 10:50 ` Morten Torstensen
2006-09-20 11:40 ` Heinz Mauelshagen
2006-09-20 12:41 ` Les Mikesell
2006-09-21 9:42 ` Heinz Mauelshagen
2006-09-21 12:52 ` Les Mikesell
2006-09-20 13:22 ` [linux-lvm] Misleading documentation (was: HDD Failure) Tobias Bluhm
2006-09-20 23:21 ` Scott Lamb
2006-09-18 19:42 ` [linux-lvm] HDD Failure Fabien Jakimowicz
2006-09-18 19:52 ` Nick
2006-09-18 19:57 ` Fabien Jakimowicz
2006-09-19 21:53 ` [linux-lvm] LVM on RAID Alexander Lazarevich
2006-09-19 22:03 ` Roger Lucas
2006-09-24 17:19 ` Nix
2006-09-19 22:04 ` Mark Krenz
2006-09-19 22:11 ` Michael Loftis
2006-09-20 0:30 ` Fabien Jakimowicz
2006-09-20 13:55 ` Matthew B. Brookover
2006-09-20 14:01 ` Michael T. Babcock
2006-09-20 14:48 ` Alexander Lazarevich
2006-09-20 15:57 ` Fabien Jakimowicz
2006-09-21 3:19 ` Andrew Boyko
2006-09-20 17:24 ` Mark H. Wood
-- strict thread matches above, loose matches on Subject: below --
2004-08-01 18:22 [linux-lvm] hdd failure Marius Gravdal
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=20060918193728.GC28043@arvo.suso.org \
--to=mark@suso.org \
--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.