From: Marcin Tomczak <marcin.tomczak@intel.com>
To: neilb@suse.de
Cc: linux-raid@vger.kernel.org, lukasz.dorau@intel.com
Subject: [PATCH] imsm: Add NO_IMSM_PLATFORM flag description to manual.
Date: Mon, 18 Feb 2013 12:51:40 +0100 [thread overview]
Message-ID: <20130218115140.2751.36089.stgit@localhost.localdomain> (raw)
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.
+
+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.
next reply other threads:[~2013-02-18 11:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-18 11:51 Marcin Tomczak [this message]
2013-03-04 6:26 ` [PATCH] imsm: Add NO_IMSM_PLATFORM flag description to manual NeilBrown
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=20130218115140.2751.36089.stgit@localhost.localdomain \
--to=marcin.tomczak@intel.com \
--cc=linux-raid@vger.kernel.org \
--cc=lukasz.dorau@intel.com \
--cc=neilb@suse.de \
/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).