Document usage of version0.91 superblock.
This commit is contained in:
parent
2a91e1491e
commit
2a940e3619
|
@ -1,3 +1,6 @@
|
|||
Changes Prior to 2.5.3 release
|
||||
- Document v0.91 superblocks in md.4
|
||||
|
||||
Changes Prior to 2.5.2 release
|
||||
- Fix problem with compiling with gcc-2 compilers
|
||||
- Fix compile problem of post-incrmenting a variable in a macro arg.
|
||||
|
|
8
md.4
8
md.4
|
@ -74,6 +74,14 @@ UUID
|
|||
a 128 bit Universally Unique Identifier that identifies the array that
|
||||
this device is part of.
|
||||
|
||||
When a version 0.90 array is being reshaped (e.g. adding extra devices
|
||||
to a RAID5), the version number is temporarily set to 0.91. This
|
||||
ensures that if the reshape process is stopped in the middle (e.g. by
|
||||
a system crash) and the machine boots into an older kernel that does
|
||||
not support reshaping, then the array will not be assembled (which
|
||||
would cause data corruption) but will be left untouched until a kernel
|
||||
that can complete the reshape processes is used.
|
||||
|
||||
.SS ARRAYS WITHOUT SUPERBLOCKS
|
||||
While it is usually best to create arrays with superblocks so that
|
||||
they can be assembled reliably, there are some circumstances where an
|
||||
|
|
Loading…
Reference in New Issue