public inbox for linux-raid@vger.kernel.org
 help / color / mirror / Atom feed
From: Goswin von Brederlow <goswin-v-b@web.de>
To: NeilBrown <neilb@suse.de>
Cc: Tim Connors <tconnors@rather.puzzling.org>,
	linux-raid@vger.kernel.org, dm-devel@redhat.com
Subject: Re: raid failure and LVM volume group availability
Date: Mon, 25 May 2009 14:15:28 +0200	[thread overview]
Message-ID: <87vdnpqsyn.fsf@frosties.localdomain> (raw)
In-Reply-To: <7df2bc4ce840fbfa8d2bec357069bc5a.squirrel@neil.brown.name> (NeilBrown's message of "Thu, 21 May 2009 13:55:03 +1000 (EST)")

"NeilBrown" <neilb@suse.de> writes:

> On Thu, May 21, 2009 1:07 pm, Tim Connors wrote:
>> Is it possible to force both lvm and md to give up on the device so I can
>> readd them without rebooting (since they're not going to be anymore
>> corrupt yet than you'd expect from an unclean shutdown, because there's
>> been no IO to them yet, so I should just be able to readd them, mount and
>> resync)?
>
> For the md side, you can just assemble the drives into an array with
> a different name.
> e.g.
>   mdadm -A /dev/md1 /dev/sda1 /dev/sd....
>
> using whatever new names were given to the devices when you plugged them
> back in.
> Maybe you can do a similar thing with the LVM side, but I know nothing
> about that.
>
> NeilBrown

On the device mapper side (the thing below lvm) you can use dmsetup to
suspend, alter and resume the device mapper table of your
devices. That should make the actual filesysems happy again.

Not sure what LVM tools will make of that though.

MfG
        Goswin

  reply	other threads:[~2009-05-25 12:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-21  3:07 raid failure and LVM volume group availability Tim Connors
2009-05-21  3:55 ` NeilBrown
2009-05-25 12:15   ` Goswin von Brederlow [this message]
2009-05-25 16:09 ` hank peng
2009-05-26 11:05   ` Goswin von Brederlow
2009-05-26 11:56     ` Neil Brown
2009-05-28 18:48       ` Goswin von Brederlow

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=87vdnpqsyn.fsf@frosties.localdomain \
    --to=goswin-v-b@web.de \
    --cc=dm-devel@redhat.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=tconnors@rather.puzzling.org \
    /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