From: Peter Smith <peter.smith@utsouthwestern.edu>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] vgchange -an question with disconnected disks
Date: Fri, 03 Feb 2006 14:01:57 -0600 [thread overview]
Message-ID: <43E3B6B5.5080409@utsouthwestern.edu> (raw)
In-Reply-To: <43E24A37.6010801@cup.hp.com>
John DeFranco wrote:
> I have a question regarding the behavior of vgchange -a n on lvm2 when
> there are disk failures. Specifically the following:
>
> 1. vgchange -a y vg00
> 2. disconnect the disks
> 3. vgchange -a n vg00
Are you doing this in the correct order? Shouldn't you _de_activate the
VG _before_ removing the disks? And besides, shouldn't you remove the
offending disks from the VG _before_ deactivating and then removing the
disks physically? Or at least something equivalent.
1. vgreduce vg00 <offending disks>
2. vgchange -a n vg00
3. disconnect the disks
4. vgchange -a y vg00
...
Peter
next prev parent reply other threads:[~2006-02-03 20:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-02 18:06 [linux-lvm] vgchange -an question with disconnected disks John DeFranco
2006-02-02 18:28 ` Alasdair G Kergon
2006-02-03 20:01 ` Peter Smith [this message]
2006-02-03 20:55 ` John DeFranco
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=43E3B6B5.5080409@utsouthwestern.edu \
--to=peter.smith@utsouthwestern.edu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).