All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Måns Rullgård" <mru@users.sourceforge.net>
To: linux-lvm@sistina.com
Subject: [linux-lvm] Re: Recovering from disk failure
Date: Thu Aug 28 13:53:02 2003	[thread overview]
Message-ID: <yw1xy8xdlin0.fsf@users.sourceforge.net> (raw)
In-Reply-To: 20030828132053.C14441@uk.sistina.com

Alasdair G Kergon <agk@uk.sistina.com> writes:

>> Recently one of two disks in a volume group crashed, and I can't read
>> it at all.  Now, some LVs are entirely on the disk that survived.  Is
>> there any way I can just disable the broken LVs and continue using the
>> complete ones?  I'm using device-mapper and LVM2
>
> Read the description of '--partial' on the lvm(8) man page.
> e.g. (lv|vg)change -ay --partial

I should have read the manuals before mailing.  However, I still have
some questions.  Some LVs were split between the two disks.  With the
--partial option, it won't let me see them at all.  Can I do something
to get just read errors, or zeros, or whatever for the missing
sectors?  I could of course do some manual work with dd, but an
automated method seems easier.

> And '--removemissing' in vgreduce(8) to *permanently* destroy
> the lost LVs (run with --test first to check what it will do).

I don't want to do that until I've salvaged all the information I can
get back.  I have plenty of scratch space on other disks.

-- 
M�ns Rullg�rd
mru@users.sf.net

  reply	other threads:[~2003-08-28 13:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-28  6:38 [linux-lvm] Recovering from disk failure Måns Rullgård
2003-08-28  7:22 ` Alasdair G Kergon
2003-08-28 13:53   ` Måns Rullgård [this message]
2003-08-28 19:32     ` [linux-lvm] " Måns Rullgård
2003-08-29  7:09     ` Alasdair G Kergon
2003-08-29 15:21       ` Måns Rullgård

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=yw1xy8xdlin0.fsf@users.sourceforge.net \
    --to=mru@users.sourceforge.net \
    --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.