Re: [PATCH 1/2] man mdadm: add information for MDADM_EXPERIMENTAL flag

[NeilBrown <neilb@suse.de>]

On Tue, 22 Mar 2011 13:10:06 +0000 Mathias Burén <mathias.buren@gmail.com>
wrote:

> On 22 March 2011 11:46, Adam Kwolek <adam.kwolek@intel.com> wrote:
> > Update man for MDADM_EXPERIMENTAL flag.
> >
> > Signed-off-by: Adam Kwolek <adam.kwolek@intel.com>
> > ---
> >
> >  mdadm.8.in |   12 ++++++++++++
> >  1 files changed, 12 insertions(+), 0 deletions(-)
> >
> > diff --git a/mdadm.8.in b/mdadm.8.in
> > index 4b70e20..96945ae 100644
> > --- a/mdadm.8.in
> > +++ b/mdadm.8.in
> > @@ -2229,6 +2229,18 @@ in a container can be converted between levels where those levels are
> >  supported by the container, and the conversion is on of those listed
> >  above.
> >
> > +Grow functionality (e.g. expand number of raid devices) for Intel's
> > +IMSM container format has experimental status. It is guarded by
> > +.B MDADM_EXPERIMENTAL
> > +environment variable. This is due to the following reasons:
> > +
> > +1. Native Intel's IMSM check-pointing is not fully implemented yet.
> > +This causes IMSM incompatibility during grow process: grew array cannot
> > +be roamed between Windows(R) and Linux systems.
> > +
> > +2. Interrupting grow operation is not recommended, because
> > +for Intel's IMSM container format it is not fully tested yet.
> > +
> >  .SS SIZE CHANGES
> >  Normally when an array is built the "size" is taken from the smallest
> >  of the drives.  If all the small drives in an arrays are, one at a
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> >
> 
> My small modifications (spelling?), which might not be correct.
> 
>  mdadm.8.in |   12 ++++++++++++
>  1 files changed, 12 insertions(+), 0 deletions(-)
> 
> diff --git a/mdadm.8.in b/mdadm.8.in
> index 4b70e20..96945ae 100644
> --- a/mdadm.8.in
> +++ b/mdadm.8.in
> @@ -2229,6 +2229,18 @@ in a container can be converted between levels
> where those levels are
>  supported by the container, and the conversion is on of those listed
>  above.
> 
> +Grow functionality (e.g. expand a number of raid devices) for Intel's
> +IMSM container format has an experimental status. It is guarded by the
> +.B MDADM_EXPERIMENTAL
> +environment variable. This is due to the following reasons:
> +
> +1. Native Intel's IMSM check-pointing is not fully implemented yet.
> +This causes IMSM incompatibility during the grow process: a grown array cannot
> +roam between Windows(R) and Linux systems.
> +
> +2. Interrupting a grow operation is not recommended, because it
> +has not been fully tested for Intel's IMSM container format yet.
> +
>  .SS SIZE CHANGES
>  Normally when an array is built the "size" is taken from the smallest
>  of the drives.  If all the small drives in an arrays are, one at a

Thanks. I included your revisions and made some more of my own :-)

See below.

NeilBrown


commit ca24ddb08da4c86b60f7e049f0b0a2c30b19c95a
Author: Adam Kwolek <adam.kwolek@intel.com>
Date:   Wed Mar 23 11:45:03 2011 +1100

    man mdadm: add information for MDADM_EXPERIMENTAL flag
    
    Update man for MDADM_EXPERIMENTAL flag.
    
    Minor revisions by Mathias Burén <mathias.buren@gmail.com> and Neil Brown.
    
    Signed-off-by: Adam Kwolek <adam.kwolek@intel.com>
    Signed-off-by: NeilBrown <neilb@suse.de>

diff --git a/mdadm.8.in b/mdadm.8.in
index 4b70e20..9537304 100644
--- a/mdadm.8.in
+++ b/mdadm.8.in
@@ -2229,6 +2229,23 @@ in a container can be converted between levels where those levels are
 supported by the container, and the conversion is on of those listed
 above.
 
+Grow functionality (e.g. expand a number of raid devices) for Intel's
+IMSM container format has an experimental status. It is guarded by the
+.B MDADM_EXPERIMENTAL
+environment variable which must be set to '1' for a GROW command to
+succeed.
+This is for the following reasons:
+
+.IP 1.
+Intel's native IMSM check-pointing is not fully implemented yet.
+This causes IMSM incompatibility during the grow process: an array
+which is growing cannot roam between Microsoft Windows(R) and Linux
+systems.
+
+.IP 2.
+Interrupting a grow operation is not recommended, because it
+has not been fully tested for Intel's IMSM container format yet.
+
 .SS SIZE CHANGES
 Normally when an array is built the "size" is taken from the smallest
 of the drives.  If all the small drives in an arrays are, one at a
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html