From: Misc Things <formisc@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Installation fails if VG is exported
Date: Tue, 7 Jun 2011 13:01:31 -0400 [thread overview]
Message-ID: <BANLkTike3yibRbLfyKhfDThUMyesBDKMnQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.LRH.2.00.1106071133440.12374@bmsred.bmsi.com>
On Tue, Jun 7, 2011 at 11:38 AM, Stuart D. Gathman <stuart@bmsi.com> wrote:
> On Tue, 7 Jun 2011, Stuart D. Gathman wrote:
> ...
> I get it - you wanted to prevent your OS experimentation from activating and
> possibly writing over your VG. �I can understand why vgexport seemed like
> a solution, but it only prevents activation and removes references from
> local LVM configuration (and prevents booting when that depends on the VG as
> you discovered).
>
> It doesn't prevent a rogue/buggy OS from scribbling on the disks. �So,
> physically disconnecting (or powering off) the disks is the best way
> to prevent that.
Right you are. i think i should reconsider my point of view - indeed
if i'm that paranoid i should eliminate any chances of losing data -
disconnect the dirve(s) is the best solution for this.
And then, i think, that the question is more relevant to anaconda
mailing group.support then to LVM group. Since it's anaconda that
tries to activate the VG.
Thank you Stuart!
Andrew
next prev parent reply other threads:[~2011-06-07 17:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-07 2:29 [linux-lvm] Installation fails if VG is exported Misc Things
2011-06-07 12:25 ` Stuart D. Gathman
2011-06-07 14:53 ` Misc Things
2011-06-07 15:25 ` Stuart D. Gathman
2011-06-07 15:38 ` Stuart D. Gathman
2011-06-07 17:01 ` Misc Things [this message]
2011-06-13 15:05 ` Andrew Z
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=BANLkTike3yibRbLfyKhfDThUMyesBDKMnQ@mail.gmail.com \
--to=formisc@gmail.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).