summaryrefslogtreecommitdiff
path: root/mdadm.8.in
Commit message (Collapse)AuthorAge
...
* Release mdadm-3.2.2NeilBrown2011-06-17
| | | | Stability release
* MAN: Man update for check-pointingAdam Kwolek2011-06-09
| | | | | Signed-off-by: Adam Kwolek <adam.kwolek@intel.com> Signed-off-by: NeilBrown <neilb@suse.de>
* Grow: accept --assume-clean with --grow --sizeNeilBrown2011-05-16
| | | | | | | When an array is resized to have larger members, --assume-clean will disable any resync if the kernel supports it (2.6.40 and later). Signed-off-by: NeilBrown <neilb@suse.de>
* Create: allow chunksize to be non-power-of-2.NeilBrown2011-05-10
| | | | | | | RAID0 has accepted chunksizes that are not a power of 2 since 2.6.30. So it time mdadm allowed that to be used. Signed-off-by: NeilBrown <neilb@suse.de>
* Finally remove auto-home-hostNeilBrown2011-04-27
| | | | | | | | This was #if-ed out for 3.0, but it really should go. Gcc 4.6.0 complains that auto_update_home is set but not used (which is true). Reported-by: Tobias Powalowski <t.powa@gmx.de>
* Release 3.2.1NeilBrown2011-03-28
| | | | Signed-off-by: NeilBrown <neilb@suse.de>
* man mdadm: Add note about auto-assembly during array reshapeAdam Kwolek2011-03-23
| | | | | | | | | 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>
* man mdadm: add information for MDADM_EXPERIMENTAL flagAdam Kwolek2011-03-23
| | | | | | | | | 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>
* Merge branch 'master' into devel-3.2NeilBrown2011-03-15
|\ | | | | | | | | | | | | | | Conflicts: Manage.c managemon.c super-ddf.c super-intel.c
| * mdadm.man: added encouragement to shrink filesystem before array.NeilBrown2011-03-15
| | | | | | | | | | | | | | Suggesting by Rory Jaffe <rsjaffe@gmail.com> to make the danger of shrinking, and to recommended avoidance technique, more explicit. Signed-off-by: NeilBrown <neilb@suse.de>
| * Assemble: add --update=no-bitmapNeilBrown2011-03-10
| | | | | | | | | | | | | | This allows an array with a corrupt internal bitmap to be assembled without the bitmap. Signed-off-by: NeilBrown <neilb@suse.de>
| * mdadm.man add encouragement to shrink filesystem before shrinking array.NeilBrown2011-03-10
| | | | | | | | | | | | | | | | Before resizing an array with --size or --array-size, then filesystem should be resized. mdadm cannot do this so the user should. Reported-by: Gavin Flower <gavinflower@yahoo.com> Signed-off-by: NeilBrown <neilb@suse.de>
| * mdadm.man: remove duplicate documentation for --array-sizeNeilBrown2011-03-02
| | | | | | | | | | | | | | | | We somehow got to version of documentation for --array-size. So merge them it one. Reported-by: Ville Skyttä <ville.skytta@iki.fi> Signed-off-by: NeilBrown <neilb@suse.de>
* | Man page updates for new --grow options.NeilBrown2011-03-10
| | | | | | | | | | | | Describe all the new ways that mdadm can reshape arrays. Signed-off-by: NeilBrown <neilb@suse.de>
* | mdadm.man add encouragement to shrink filesystem before shrinking array.NeilBrown2011-02-15
| | | | | | | | | | | | | | | | Before resizing an array with --size or --array-size, then filesystem should be resized. mdadm cannot do this so the user should. Reported-by: Gavin Flower <gavinflower@yahoo.com> Signed-off-by: NeilBrown <neilb@suse.de>
* | Release mdadm-3.2 - developer only releaseNeilBrown2011-02-01
| | | | | | | | Signed-off-by: NeilBrown <neilb@suse.de>
* | Various man page fixes.NeilBrown2011-02-01
| | | | | | | | Signed-off-by: NeilBrown <neilb@suse.de>
* | Man pages update for policy frameworkPrzemyslaw Czarnowski2011-01-31
| | | | | | | | | | | | | | | | | | Includes description of POLICY line in /etc/mdadm.conf and of changes in Monitor and Incremental related to autorebuild. Signed-off-by: Anna Czarnowska <anna.czarnowska@intel.com> Signed-off-by: Przemyslaw Czarnowski <przemyslaw.hawrylewicz.czarnowski@intel.com> Signed-off-by: NeilBrown <neilb@suse.de>
* | Allow --update=devicesize with --re-addNeilBrown2010-12-09
| | | | | | | | | | | | | | | | | | | | This is useful with 1.1 and 1.2 metadata to update the metadata if the device size has changed. The same functionality can be achieved by writing to the device size in sysfs after re-adding normally, but in some cases this might be easier. Signed-off-by: NeilBrown <neilb@suse.de>
* | Merge branch 'master' into devel-3.2NeilBrown2010-12-09
|\| | | | | | | | | | | | | | | Conflicts: mdadm.8.in Same conceptual change was written with different words in each version. Signed-off-by: NeilBrown <neilb@suse.de>
| * mdadm.8: man page improvements concerning reshape and metadata types.John Robinson2010-11-02
| | | | | | | | | | | | | | | | - other differences between 0.90 and 1.x metadata explained - reshape text enhanced to properly acknowledge shrinks and in-place reshapes, particularly in the context of --backup-file. Signed-off-by: NeilBrown <neilb@suse.de>
* | Assemble: allow an array undergoing reshape to be started without backup fileNeilBrown2010-12-01
| | | | | | | | | | | | | | | | | | Though not having the proper backup file can cause data corruption, it is not enough to justify not being able to start the array at all. So allow "--invalid-backup" to be specified which says "just continue even if a backup cannot be restored". Signed-off-by: NeilBrown <neilb@suse.de>
* | Assemble: add --update=no-bitmapNeilBrown2010-11-30
| | | | | | | | | | | | | | This allows an array with a corrupt internal bitmap to be assembled without the bitmap. Signed-off-by: NeilBrown <neilb@suse.de>
* | Allow K,M,G suffix on chunk sizes as well as device/array sizes.NeilBrown2010-11-30
|/ | | | | | | | | | We already allow K,M,G suffixes for --size and --array-size. Allow it for --chunk and --bitmap-chunk as well. Also add this info to man page, and remove the duplication of info about --array-size. Signed-off-by: NeilBrown <neilb@suse.de>
* Release mdadm-3.1.4NeilBrown2010-08-31
| | | | | | bugfix/stability. Signed-off-by: NeilBrown <neilb@suse.de>
* Release mdadm-3.1.3NeilBrown2010-08-06
| | | | | Signed-off-by: NeilBrown <neilb@suse.de>
* Improve --re-add documentationNeilBrown2010-07-07
| | | | | | | and add the fact that --test can now be used with --manage operations. Signed-off-by: NeilBrown <neilb@suse.de>
* Merge branch 'master' of git://github.com/djbw/mdadmNeilBrown2010-07-06
|\
| * Merge branch 'fixes' into for-neilDan Williams2010-07-01
| |
* | Add support for "--re-add missing"NeilBrown2010-07-06
| | | | | | | | | | | | | | | | | | | | | | | | | | | | If the device name "missing" is given for --re-add, then mdadm will attempt to find any device which should be a member of the array but currently isn't and will --re-add it to the array. This can be useful if a device disappeared due to a cabling problem, and was then re-connected. The appropriate sequence would be mdadm /dev/mdX --fail detached mdadm /dev/mdX --remove detached mdadm /dev/mdX --re-add missing Signed-off-by: NeilBrown <neilb@suse.de>
* | Add -fail support to --incrementalNeilBrown2010-06-30
| | | | | | | | | | | | | | | | | | | | | | | | | | This can be used for hot-unplug. When a device has been remove, udev can call mdadm --incremental --fail sda and mdadm will find the array holding sda and remove sda from the array. Based on code from Doug Ledford <dledford@redhat.com> Signed-off-by: NeilBrown <neilb@suse.de>
* | Correct documentation for --rebuild-mapNeilBrown2010-06-30
|/ | | | | | | | | | In some places it is referred to as "--rebuild", and while that works due to getopt allowing prefixes, it could appear confusing (rebuild means other things too) and being explicit is some safeguard if we want to add e.g. --rebuild-foo later. Reported-by: Doug Ledford <dledford@redhat.com> Signed-off-by: NeilBrown <neilb@suse.de>
* Fix man page reference to --level changes with --grow.NeilBrown2010-05-31
| | | | | | | --level can be used with --grow now, so correct man page. Reported-by: "Leslie Rhorer" <lrhorer@satx.rr.com> Signed-off-by: NeilBrown <neilb@suse.de>
* Compile-time switch to enable 0.9 metadata as defaultmartin f. krafft2010-05-31
This commit introduces DEFAULT_OLD_METADATA as a preprocessor definition. If defined, it causes mdadm to assume metadata version 0.9 as default. If not defined, version 1.x (currently 1.2) is used as default. The man page mdadm.8 is also modified to reflect the chosen default. The selftests will not work if the old default is chosen. This patch was requested by Debian so they could distribute a current mdadm together with boot loaders that only understand 0.90 metadata for md-raid. Preferred usage is simply make DEFAULT_OLD_METADATA=yes Signed-off-by: martin f. krafft <madduck@debian.org> Signed-off-by: NeilBrown <neilb@suse.de>
generated by cgit v1.2.3 (git 2.25.1) at 2024-05-17 08:54:41 +0000