summaryrefslogtreecommitdiffstats
path: root/mdadm.8.in (follow)
Commit message (Collapse)AuthorAgeFilesLines
...
* mdadm:add man page for --symlinksZhilong Liu2017-03-061-0/+9
| | | | | | | | | | | | | In build and create mode: --symlinks Auto creation of symlinks in /dev to /dev/md, option --symlinks must be 'no' or 'yes' and work with --create and --build. In assemble mode: --symlinks See this option under Create and Build options. Signed-off-by: Zhilong Liu <zlliu@suse.com> Signed-off-by: Jes Sorensen <Jes.Sorensen@gmail.com>
* Release mdadm-4.0mdadm-4.0Jes Sorensen2017-01-091-1/+1
| | | | | | My first release! Signed-off-by: Jes Sorensen <Jes.Sorensen@gmail.com>
* Add failfast support.NeilBrown2016-11-281-1/+31
| | | | | | | | | | | | | Allow per-device "failfast" flag to be set when creating an array or adding devices to an array. When re-adding a device which had the failfast flag, it can be removed using --nofailfast. failfast status is printed in --detail and --examine output. Signed-off-by: NeilBrown <neilb@suse.com> Signed-off-by: Jes Sorensen <Jes.Sorensen@redhat.com>
* mdadm: add man page for --add-journalSong Liu2016-08-121-0/+8
| | | | | | | | | | | | | | | | Add the following to man page: --add-journal Recreate journal for RAID-4/5/6 array that lost a journal device. In the current implementation, this command cannot add a journal to an array that had a failed journal. To avoid interrupting on-going write opertion --add-journal only works for array in Read-Only state. Reported-by: Yi Zhang <yizhan@redhat.com> Signed-off-by: Song Liu <songliubraving@fb.com> Signed-off-by: Shaohua Li <shli@fb.com> Signed-off-by: Jes Sorensen <Jes.Sorensen@redhat.com>
* Consistent use of metric prefix in manpageMarko Hauptvogel2016-04-011-7/+8
| | | | | | | | Added the optional K suffix for completeness, as it is allowed by util.c's parse_size(char*). Signed-off-by: Marko Hauptvogel <marko.hauptvogel@googlemail.com> Signed-off-by: Jes Sorensen <Jes.Sorensen@redhat.com>
* Release mdadm-3.4mdadm-3.4NeilBrown2016-01-281-1/+1
| | | | | | My last release! Signed-off-by: NeilBrown <neilb@suse.com>
* Fix wrong description in manpageGuoqing Jiang2016-01-121-4/+4
| | | | | | | | | The careless change was introduce by 'commit 7e6e839a2651 (mdadm: change the num of cluster node)'. Which should be revert to avoid misunderstanding. Signed-off-by: Guoqing Jiang <gqjiang@suse.com> Signed-off-by: NeilBrown <neilb@suse.com>
* Add help message and man entry for --write-journalSong Liu2015-10-191-0/+6
| | | | | | Signed-off-by: Song Liu <songliubraving@fb.com> Signed-off-by: Shaohua Li <shli@fb.com> Signed-off-by: NeilBrown <neilb@suse.com>
* Merge branch 'mdadm-3.3.x'NeilBrown2015-08-031-1/+1
|\
| * Release mdadm-3.3.4mdadm-3.3.4NeilBrown2015-08-031-1/+1
| | | | | | | | | | | | Important bugfix release. Signed-off-by: NeilBrown <neilb@suse.com>
* | Merge branch 'cluster'NeilBrown2015-07-271-1/+41
|\ \ | |/ |/| | | | | | | Now that 3.3.3 is out, it is time to include the cluster-support code. Signed-off-by: NeilBrown <neilb@suse.com>
| * mdadm: change the num of cluster nodeGuoqing Jiang2015-06-171-0/+8
| | | | | | | | | | | | | | | | | | | | | | | | This extends nodes option for assemble mode, make the num of cluster node could be change by user. Before that, it is necessary to ensure there are enough space for those nodes, calc_bitmap_size is introduced to calculate the bitmap size of each node. Signed-off-by: Guoqing Jiang <gqjiang@suse.com> Signed-off-by: NeilBrown <neilb@suse.de>
| * mdadm: add the ability to change cluster nameGuoqing Jiang2015-06-171-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | To support change the cluster name, the commit do the followings: 1. extend original write_bitmap function for new scenario. 2. add the scenarion to handle the modification of cluster's name in write_bitmap1. 3. let the cluster name also show in examine_super1 and detail_super1 Signed-off-by: Guoqing Jiang <gqjiang@suse.com> Signed-off-by: NeilBrown <neilb@suse.de>
| * Add a new clustered diskGuoqing Jiang2015-06-171-0/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | A clustered disk is added by the traditional --add sequence. However, other nodes need to acknowledge that they can "see" the device. This is done by --cluster-confirm: --cluster-confirm SLOTNUM:/dev/whatever (if disk is found) or --cluster-confirm SLOTNUM:missing (if disk is not found) The node initiating the --add, has the disk state tagged with MD_DISK_CLUSTER_ADD and the one confirming tag the disk with MD_DISK_CANDIDATE. Signed-off-by: Goldwyn Rodrigues <rgoldwyn@suse.com> Signed-off-by: Guoqing Jiang <gqjiang@suse.com> Signed-off-by: NeilBrown <neilb@suse.de>
| * Set home-cluster while creating an arrayGuoqing Jiang2015-06-171-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The home-cluster is stored in the bitmap super block of the array. The device can be assembled on a cluster with the cluster name same as the one recorded in the bitmap. If home-cluster is not specified, this is auto-detected using dlopen corosync cmap library. neilb: allow code to compile when corosync-devel is not installed. Signed-off-by: Goldwyn Rodrigues <rgoldwyn@suse.com> Signed-off-by: Guoqing Jiang <gqjiang@suse.com> Signed-off-by: NeilBrown <neilb@suse.de>
| * Add nodes option while creating mdGuoqing Jiang2015-06-171-0/+6
| | | | | | | | | | | | | | | | | | | | Specifies the maximum number of nodes in the cluster that may use this device simultaneously. This is equivalent to the number of bitmaps created in the internal superblock (patches to follow). Signed-off-by: Goldwyn Rodrigues <rgoldwyn@suse.com> Signed-off-by: Guoqing Jiang <gqjiang@suse.com> Signed-off-by: NeilBrown <neilb@suse.de>
| * Create n bitmaps for clustered modeGuoqing Jiang2015-06-161-1/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | For a clustered MD, create bitmaps equal to number of nodes so each node has an independent bitmap. Only the first bitmap is has the bits set so that the first node that assembles the device also performs the sync. The bitmaps are aligned to 4k boundaries. On-disk format: 0 4k 8k 12k ------------------------------------------------------------------- | idle | md super | bm super [0] + bits | | bm bits[0, contd] | bm super[1] + bits | bm bits[1, contd] | | bm super[2] + bits | bm bits [2, contd] | bm super[3] + bits | | bm bits [3, contd] | | | Signed-off-by: Goldwyn Rodrigues <rgoldwyn@suse.com> Signed-off-by: Guoqing Jiang <gqjiang@suse.com> Signed-off-by: NeilBrown <neilb@suse.de>
* | Release mdadm-3.3.3mdadm-3.3.3NeilBrown2015-07-241-1/+1
| | | | | | | | Signed-off-by: NeilBrown <neilb@suse.com>
* | mdadm: document --homehost=any functionality.NeilBrown2015-07-221-0/+7
| | | | | | | | Signed-off-by: NeilBrown <neilb@suse.com>
* | Remove some trailing white spaceNeilBrown2015-07-021-2/+2
|/ | | | | | It looks ugly in my editor. Signed-off-by: NeilBrown <neilb@suse.de>
* Fix minor typo in mdadm manpage.Andrew Burgess2015-05-231-1/+1
| | | | | | | | | | | Appologies if this is the wrong mailing list for this patch. This is a very small patch for the manual page for the mdadm utility. Thanks, Andrew Signed-off-by: NeilBrown <neilb@suse.de>
* Release mdadm-3.3.2mdadm-3.3.2NeilBrown2014-08-211-1/+1
| | | | | | Minor bugfix/stability release. Signed-off-by: NeilBrown <neilb@suse.de>
* mdadm: document some more magic environment variables.NeilBrown2014-08-141-0/+26
| | | | | | Others are mostly for developers. Signed-off-by: NeilBrown <neilb@suse.de>
* mdadm.8: Fix typo in setting font.NeilBrown2014-07-031-1/+1
| | | | | | \fP returns to previous font, not \fp. Signed-off-by: NeilBrown <neilb@suse.de>
* mdadm.8: Fix typo in "no-bbl".NeilBrown2014-07-031-1/+1
| | | | | | The '\' comes before the '-', not after! Signed-off-by: NeilBrown <neilb@suse.de>
* Release mdadm-3.3.1mdadm-3.3.1NeilBrown2014-06-051-1/+1
| | | | Signed-off-by: NeilBrown <neilb@suse.de>
* MISC: add --action option to set or abort check/repair.NeilBrown2014-05-221-0/+25
| | | | Signed-off-by: NeilBrown <neilb@suse.de>
* Clarify scope of Rebuild events in mdadm manpageJan Ceuleers2013-12-121-1/+2
| | | | | | | | | | | | | | To date, the manpage did not make it clear under which circumstances Rebuild events are generated, leading to a question on the mailing list as to whether it is normal for these events to be generated while checking an array. So clarify that all operations that act on the entire array are in scope. The list is given as "e.g.", because it might grow in the future as other full-array operations are added. Reported-by: Mark Knecht <markknecht@gmail.com> Signed-off-by: Jan Ceuleers <jan.ceuleers@computer.org> Signed-off-by: NeilBrown <neilb@suse.de>
* Incremental: improve support for "DEVICE" based restriction in mdadm.confNeilBrown2013-12-031-2/+10
| | | | | | | | | | | | | | | | | --incremental currently fails if the device name passed does not textually match the names permitted by the DEVICE line in mdadm.conf. This is problematic when "mdadm -I" is run by udev as the name given can be a temp name. This patch makes two improvements: 1/ We generate a list of all existing devices that match the names in mdadm.conf, and allow rdev based matching 2/ We allows extra aliases to be provided on the command line, and perform textual matching on those. This is particularly suitable for udev usages as ${DEVLINKS} can be provided even though the links make not yet be created. Signed-off-by: NeilBrown <neilb@suse.de>
* Incremental: add --export handling.NeilBrown2013-11-281-2/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | If --export is given with --incremental, then MD_DEVNAME is output which gives the name of the device (in /dev/md) that is the array (or container) that the device would be added to. Also MD_STARTED is set to one of no unsafe yes nothing to indicate if the array was started. IF MD_STARTED=unsafe then it may be appropriate to run mdadm -R /dev/md/$MD_DEVNAME after a timeout to ensure newly degraded array are started. If MD_FOREIGN=yes it might be appropriate to suppress this as the array is probably not critical. Signed-off-by: NeilBrown <neilb@suse.de>
* Add support for --add-spareNeilBrown2013-10-311-0/+12
| | | | | | | | | | --add-spare is like --add, but a --re-add is never attempted. So it is equivalent to two separate commands: --zero-metadata --add Signed-off-by: NeilBrown <neilb@suse.de>
* Fix typos in mdadm.8.inJohn Schmidt2013-10-291-1/+1
| | | | | | | | I found a small bug in the documentation of mdadm. I fixed it in my local git clone of git://neil.brown.name/mdadm Here is the change: Signed-off-by: NeilBrown <neilb@suse.de>
* Release mdadm-3.3mdadm-3.3NeilBrown2013-09-031-1/+1
| | | | | | (and various cosmetic fixes) Signed-off-by: NeilBrown <neilb@suse.de>
* config: support MDADM_CONF_AUTO= env var.NeilBrown2013-09-031-0/+22
| | | | | | | | | | | | | If a distribution allows the choice between using mdadm and dmraid for DDF and IMSM to be made by some config file (/etc/defaults/ /sys/sysconfig/ etc) which is queried by /etc/init.d scripts, then the fact that mdadm implements this choce through the config file is not very helpful. So allow the "AUTO" line to be specified in part using MDADM_CONF_AUTO in environment. Signed-off-by: NeilBrown <neilb@suse.de>
* config: read /etc/mdadm.conf.d as well as /etc/mdadm.confNeilBrown2013-09-031-5/+23
| | | | | | | | | | | | | If a configfile is explicitly given, just that file or directory is read. Otherwise we now read both a file /etc/mdadm.conf and a directory /etc/mdadm.conf.d This allows a transition to directory based config, which in turn allows easy control from scripts. Signed-off-by: NeilBrown <neilb@suse.de>
* mdadm.8: growing RAID10 chunk size is possibleChristoph Anton Mitterer2013-07-081-2/+2
| | | | Signed-off-by: NeilBrown <neilb@suse.de>
* mdadm.8.in: Fix typo: previous -> previouslyNeilBrown2013-07-021-1/+1
| | | | | Signed-off-by: Wieland Hoffmann <themineo@gmail.com> Signed-off-by: NeilBrown <neilb@suse.de>
* Assemble: --update=metadata converts v0.90 to v1.0NeilBrown2013-05-281-1/+17
| | | | | | | | | | This allows the smooth conversion of legacy 0.90 arrays to 1.0 metadata. Old metadata is likely to remain but will be ignored. It can be removed with mdadm --zero-superblock --metadata=0.90 /dev/whatever Signed-off-by: NeilBrown <neilb@suse.de>
* Add --dump / --restore functionality.NeilBrown2013-05-161-0/+49
| | | | | | | | This allows the metadata on a device to be saved and later restored. This can be useful before experimenting on an array that is misbehaving. Suggested-by: Dan Williams <dan.j.williams@intel.com> Signed-off-by: NeilBrown <neilb@suse.de>
* man pages: remove references to raidtools.NeilBrown2013-05-151-25/+0
| | | | | | raidtools is so ancient now that it is uninteresting. Signed-off-by: NeilBrown <neilb@suse.de>
* create_mddev: add support for /dev/md_XXX non-numeric names.NeilBrown2013-05-151-7/+21
| | | | | | | | | | With the 'devnm' infrastructure fixed, it is quite easy to support names like "md_home" for md arrays. The currently defaults to "off" and can be enabled in mdadm.conf with CREATE names=yes This is incase other tools get confused by the new names. Signed-off-by: NeilBrown <neilb@suse.de>
* Manage: support --fail set-X and --remove set-XNeilBrown2013-05-131-6/+26
| | | | | | | | A RAID10 array can have 'sets' of devices which are reported by --detail. They can now be collectively failed or removed. Signed-off-by: NeilBrown <neilb@suse.de>
* Create: default to bitmap=internal for large arrays.NeilBrown2013-03-051-0/+15
| | | | | | | | Here, "large" means components are 100G or more. It is usually beneficial to have write-intent bitmaps on such arrays. They can be suppressed with --bitmap=none Signed-off-by: NeilBrown <neilb@suse.de>
* mdadm.8: Detail use for IMSM_NO_PLATFORM environment variable.NeilBrown2013-03-041-0/+15
| | | | Suggested-by: Marcin Tomczak <marcin.tomczak@intel.com>
* Remove --offroot argument and default to always setting argv[0] to @Jes Sorensen2013-02-051-11/+0
| | | | | | | | | | | We still allow --offroot to be given - for compatibility with scripts - but ignore it. The whole point of --offroot is to get systemd to not auto-kill mdmon, and we always want that. Signed-off-by: Jes Sorensen <Jes.Sorensen@redhat.com> Signed-off-by: NeilBrown <neilb@suse.de>
* MISC: Add --examine-badblocks optionNeilBrown2012-12-051-0/+7
| | | | | | This will list the contents of the bad-blocks log, if one is present. Signed-off-by: NeilBrown <neilb@suse.de>
* Manage: Add support for --re-add faultyNeilBrown2012-11-281-1/+13
| | | | | | | | | mdadm /dev/mdXX --re-add faulty will identify any faulty devices in the array, remove them, and --re-add them. Signed-off-by: NeilBrown <neilb@suse.de>
* Add support for --replace and --withNeilBrown2012-10-231-2/+22
| | | | | | | | | --replace can be used to replace a device without completely failing it. Once the replacement completes the device will be failed. --with can indicate which of several spares to use. Signed-off-by: NeilBrown <neilb@suse.de>
* Trivial bugfix and spelling fixes.Michael Tokarev2012-10-211-26/+0
| | | | | | | | | And here's another trivial bugfix, now for spelling mistakes in various places, authred by Sergey Kirpichev (Cc'ed) and carried in debian mdadm package. Signed-off-by: NeilBrown <neilb@suse.de>
* Allow data-offset to be specified per-device for createNeilBrown2012-10-041-1/+12
| | | | | | | | | mdadm --create /dev/md0 .... /dev/sda1:1024 /dev/sdb1:2048 ... The size is in K unless a suffix: K M G is given. The suffix 's' means sectors. Signed-off-by: NeilBrown <neilb@suse.de>
generated by cgit v1.2.3 (git 2.39.1) at 2025-01-18 12:00:46 +0100