From: Jonathan E Brassow <jbrassow@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] lvm2 *TEMPORARY* PV failure - what happens?
Date: Wed, 26 Apr 2006 11:08:18 -0500 [thread overview]
Message-ID: <8bfc154a0fd2cf17f26b10f32c9194e0@redhat.com> (raw)
In-Reply-To: <1146005699.26842.166.camel@localhost.localdomain>
On Apr 25, 2006, at 5:54 PM, Ming Zhang wrote:
>> I'm still wondering if the disk comes back if the LV will be available
>> again, or if LVM will mark it as failed, and assume that all blocks on
>
> it will not automatically available i think, but with that "echo ...",
> u
> might be able to see it again.
>
Actually, I think it is available once the dev comes back.
brassow
prev parent reply other threads:[~2006-04-26 16:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-25 19:08 [linux-lvm] lvm2 *TEMPORARY* PV failure - what happens? Ty! Boyack
2006-04-25 19:57 ` Ming Zhang
2006-04-25 20:21 ` Jonathan E Brassow
2006-04-25 20:39 ` Ming Zhang
2006-04-25 21:34 ` Jonathan E Brassow
2006-04-25 21:44 ` Ming Zhang
2006-04-25 22:13 ` Ty! Boyack
2006-04-25 22:54 ` Ming Zhang
2006-04-26 16:08 ` Jonathan E Brassow [this message]
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=8bfc154a0fd2cf17f26b10f32c9194e0@redhat.com \
--to=jbrassow@redhat.com \
--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).