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

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

[Adam Kwolek]

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

[PATCH 2/2] man mdadm: Add note about auto-assembly during array reshape

[Adam Kwolek]

Add note to man that auto-assembly cannot be used for reshaped arrays.

Signed-off-by: Adam Kwolek <adam.kwolek@intel.com>
---

 mdadm.8.in |    6 ++++++
 1 files changed, 6 insertions(+), 0 deletions(-)

diff --git a/mdadm.8.in b/mdadm.8.in
index 96945ae..2285d4f 100644
--- a/mdadm.8.in
+++ b/mdadm.8.in
@@ -1665,6 +1665,12 @@ The reason for requiring arrays to be tagged with the homehost for
 auto assembly is to guard against problems that can arise when moving
 devices from one host to another.
 ..
+Note: Auto assembly cannot be used for assembling and activating arrays
+under reshape.
+.B Scan
+doesn't allow for
+.B backup\-file
+passing, required by reshape restart and continuation.
 
 .SH BUILD MODE
 

Re: [PATCH 2/2] man mdadm: Add note about auto-assembly during array reshape

[NeilBrown]

On Tue, 22 Mar 2011 12:46:43 +0100 Adam Kwolek <adam.kwolek@intel.com> wrote:

> Add note to man that auto-assembly cannot be used for reshaped arrays.
> 
> Signed-off-by: Adam Kwolek <adam.kwolek@intel.com>
> ---
> 
>  mdadm.8.in |    6 ++++++
>  1 files changed, 6 insertions(+), 0 deletions(-)
> 
> diff --git a/mdadm.8.in b/mdadm.8.in
> index 96945ae..2285d4f 100644
> --- a/mdadm.8.in
> +++ b/mdadm.8.in
> @@ -1665,6 +1665,12 @@ The reason for requiring arrays to be tagged with the homehost for
>  auto assembly is to guard against problems that can arise when moving
>  devices from one host to another.
>  ..
> +Note: Auto assembly cannot be used for assembling and activating arrays
> +under reshape.
> +.B Scan
> +doesn't allow for
> +.B backup\-file
> +passing, required by reshape restart and continuation.
>  
>  .SH BUILD MODE
>  

Applied with some revisions - thanks.

NeilBrown

commit 246cebdb7601fc41ee0cca9a5379cdd7dc072380
Author: Adam Kwolek <adam.kwolek@intel.com>
Date:   Wed Mar 23 12:02:28 2011 +1100

    man mdadm: Add note about auto-assembly during array reshape
    
    Add note to man that auto-assembly cannot be used for reshaped arrays.
    
    Revisions: NeilBrown
    
    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 9537304..982991d 100644
--- a/mdadm.8.in
+++ b/mdadm.8.in
@@ -1665,6 +1665,13 @@ The reason for requiring arrays to be tagged with the homehost for
 auto assembly is to guard against problems that can arise when moving
 devices from one host to another.
 ..
+Note: Auto assembly cannot be used for assembling and activating some
+arrays which are undergoing reshape.  In particular as the
+.B backup\-file
+cannot be given, any reshape which requires a backup-file to continue
+cannot be started by auto assembly.  An array which is growing to more
+devices and has passed the critical section can be assembled using
+auto-assembly.
 
 .SH BUILD MODE
 

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

[Mathias Burén]

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


// Mathias
--
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

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

[NeilBrown]

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