From: NeilBrown <neilb@suse.de>
To: Marcin Tomczak <marcin.tomczak@intel.com>
Cc: linux-raid@vger.kernel.org, lukasz.dorau@intel.com
Subject: Re: [PATCH] imsm: Add NO_IMSM_PLATFORM flag description to manual.
Date: Mon, 4 Mar 2013 17:26:32 +1100 [thread overview]
Message-ID: <20130304172632.1168644a@notabene.brown> (raw)
In-Reply-To: <20130218115140.2751.36089.stgit@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 2452 bytes --]
On Mon, 18 Feb 2013 12:51:40 +0100 Marcin Tomczak <marcin.tomczak@intel.com>
wrote:
> In exceptional cases user can use NO_IMSM_PLATFORM flag to use IMSM
> metadata RAIDs without valid Intel platform. With this flag set
> mdadm does not perform any compatibility checks.
>
> Note: Usage of this flag may lead to data loss!
>
> Signed-off-by: Marcin Tomczak <marcin.tomczak@intel.com>
> ---
> mdadm.8.in | 19 +++++++++++++++++++
> 1 files changed, 19 insertions(+), 0 deletions(-)
>
> diff --git a/mdadm.8.in b/mdadm.8.in
> index 535cc39..3ef20c7 100644
> --- a/mdadm.8.in
> +++ b/mdadm.8.in
> @@ -2714,6 +2714,25 @@ to '1', the
> .I mdadm
> will create and devices that are needed.
>
> +.TP
> +.B IMSM_NO_PLATFORM
> +ATTENTION! Usage of this flag is extremely dangerous! You should use
> +this flag only when you know what you are doing and when it is
> +necessary. Make a backup before any action. You use it on your own
> +responsibility - unpredictable effects may appear much later.
I'm sorry, but I'm not going to include that sort of hyperbole in the man
page. A simple statement of what it does is sufficient.
I have applied this patch.
NeilBrown
From 401f095c39b732b4247bd728cb493eb7bb692298 Mon Sep 17 00:00:00 2001
From: NeilBrown <neilb@suse.de>
Date: Mon, 4 Mar 2013 17:25:36 +1100
Subject: [PATCH] mdadm.8: Detail use for IMSM_NO_PLATFORM environment
variable.
Suggested-by: Marcin Tomczak <marcin.tomczak@intel.com>
diff --git a/mdadm.8.in b/mdadm.8.in
index a3abc2d..1c06533 100644
--- a/mdadm.8.in
+++ b/mdadm.8.in
@@ -2710,6 +2710,21 @@ to '1', the
.I mdadm
will create and devices that are needed.
+.TP
+.B IMSM_NO_PLATFORM
+A key value of IMSM metadata is that it allows interoperability with
+boot ROMs on Intel platforms, and with other major operating systems.
+Consequently,
+.I mdadm
+will only allow an IMSM array to be created or modified if detects
+that it is running on an Intel platform which supports IMSM, and
+supports the particular configuration of IMSM that is being requested
+(some functionality requires newer OROM support).
+
+These checks can be suppressed by setting IMSM_NO_PLATFORM=1 in the
+environment. This can be useful for testing or for disaster
+recovery. You should be aware that interoperability may be
+compromised by setting this value.
.SH EXAMPLES
.B " mdadm \-\-query /dev/name-of-device"
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
prev parent reply other threads:[~2013-03-04 6:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-18 11:51 [PATCH] imsm: Add NO_IMSM_PLATFORM flag description to manual Marcin Tomczak
2013-03-04 6:26 ` NeilBrown [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=20130304172632.1168644a@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=lukasz.dorau@intel.com \
--cc=marcin.tomczak@intel.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).