All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bryn M. Reeves" <bmr@redhat.com>
To: Alireza Nematollahi <alirezan@sfu.ca>
Cc: device-mapper development <dm-devel@redhat.com>
Subject: Re: Stopped disk causes LVM to go crazy
Date: Wed, 11 Feb 2009 18:50:45 +0000	[thread overview]
Message-ID: <49931E05.2010901@redhat.com> (raw)
In-Reply-To: <798685706.2823991234377915224.JavaMail.root@jaguar7.sfu.ca>

Alireza Nematollahi wrote:
> hi. Thanks for your reply. Well, I had tried that before, but no luck. I tried it again, and still no luck: 

You have to do it *BEFORE* you disable/remove the storage. Doing it 
afterwards will just throw all the errors you are seeing since the LVM 
tools can no longer access the device.

You have to do things in the correct order; first unmount any file 
systems, then de-activate LVs/VGs, then stop or remove the storage 
hardware.

If you do this in the wrong order you'll end up with the problems 
you're seeing.

For now, you can clean up /dev/sdb by deleting it via sysfs:

echo 1 > /sys/block/sdb/device/delete

Which will stop other commands that scan the disks from tripping over 
the dead device. You can also manually delete any remaining device 
mapper devices that reference the removed disk (see similar thread 
yesterday).

Regards,
Bryn.

  reply	other threads:[~2009-02-11 18:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <940984053.2821991234377736540.JavaMail.root@jaguar7.sfu.ca>
2009-02-11 18:45 ` Stopped disk causes LVM to go crazy Alireza Nematollahi
2009-02-11 18:50   ` Bryn M. Reeves [this message]
     [not found] <288159352.2860111234381750007.JavaMail.root@jaguar7.sfu.ca>
2009-02-11 20:04 ` Alireza Nematollahi
2009-02-13  9:52   ` Nuno Fernandes
2009-02-10 23:31 Alireza Nematollahi
2009-02-11 10:39 ` Bryn M. Reeves

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=49931E05.2010901@redhat.com \
    --to=bmr@redhat.com \
    --cc=alirezan@sfu.ca \
    --cc=dm-devel@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.