imsm: Add NO_IMSM_PLATFORM flag description to manual.
PATCH 1/1 imsm: Add NO_IMSM_PLATFORM flag description to manual.
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!
--- mdadm.8.in | 19 +++++++++++++++++++ 1 files changed, 19 insertions(+), 0 deletions(-)
mdadm.8.in +19 -0
@@ -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. + +The IMSM_NO_PLATFORM flag concerns only IMSM metadata. By default, IMSM +metadata is supported only by Intel based platforms with OROM and it's +shared between Linux, Microsoft Windows and OROM, thus you can switch +between these environments safely. When you use a mdadm command and the +value of the flag is set to '1', then mdadm does not care about the +hardware configuration and OROM restrictions. It may cause a +compatibility problem and OROM or Windows can, for example, set the +state of the RAID volume to failed and then you may lose all your data. +Other possible scenario is that created RAID Volume will be +incompatible with target platform's OROM and volume will not be +assembled on that platform. + .SH EXAMPLES .B " mdadm \-\-query /dev/name-of-device"
---------------------------------------------------------------------
Intel Technology Poland sp. z o.o.
z siedziba w Gdansku
ul. Slowackiego 173
80-298 Gdansk
Sad Rejonowy Gdansk Polnoc w Gdansku,
VII Wydzial Gospodarczy Krajowego Rejestru Sadowego, numer KRS 101882
NIP 957-07-52-316
Kapital zakladowy 200.000 zl
This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.
Quoted 16 lines · On Mon, 18 Feb 2013 12:51:40 +0100 Marcin Tomczak <[email protected]>…
In exceptional cases user can use
NO_IMSM_PLATFORMflag 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 <[email protected]>--- mdadm.8.in | 19 +++++++++++++++++++ 1 files changed, 19 insertions(+), 0 deletions(-)mdadm.8.in +0
-0
mdadm.8.in to '1', the · line 2722
Quoted 9 lines
mdadm.8.in +6
-0@@ -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 <[email protected]>
Date: Mon, 4 Mar 2013 17:25:36 +1100
Subject: [PATCH] mdadm.8: Detail use for IMSM_NO_PLATFORM environment
variable.
mdadm.8.in +15 -0
@@ -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"