FM / mdadm

/usr/share/doc/mdadm

Name	Size	Mode	Actions
examples/	-	0755	rm
ANNOUNCE-3.0	3486	0644	edit dl rm
ANNOUNCE-3.0.1	620	0644	edit dl rm
ANNOUNCE-3.0.2	583	0644	edit dl rm
ANNOUNCE-3.0.3	1009	0644	edit dl rm
ANNOUNCE-3.1	1164	0644	edit dl rm
ANNOUNCE-3.1.1	1442	0644	edit dl rm
ANNOUNCE-3.1.2	1795	0644	edit dl rm
ANNOUNCE-3.1.3	1933	0644	edit dl rm
ANNOUNCE-3.1.4	1332	0644	edit dl rm
ANNOUNCE-3.1.5	1792	0644	edit dl rm
ANNOUNCE-3.2	3014	0644	edit dl rm
ANNOUNCE-3.2.1	3313	0644	edit dl rm
ANNOUNCE-3.2.2	1546	0644	edit dl rm
ANNOUNCE-3.2.3	810	0644	edit dl rm
ANNOUNCE-3.2.4.gz	3696	0644	edit dl rm
ANNOUNCE-3.2.5	1046	0644	edit dl rm
ANNOUNCE-3.2.6	2664	0644	edit dl rm
ANNOUNCE-3.3	2752	0644	edit dl rm
ANNOUNCE-3.3.1	826	0644	edit dl rm
ANNOUNCE-3.3.2	467	0644	edit dl rm
ANNOUNCE-3.3.3	577	0644	edit dl rm
ANNOUNCE-3.3.4	1518	0644	edit dl rm
ANNOUNCE-3.4	888	0644	edit dl rm
ANNOUNCE-4.0	852	0644	edit dl rm
ANNOUNCE-4.1	551	0644	edit dl rm
ANNOUNCE-4.2	716	0644	edit dl rm
changelog.Debian.gz	2370	0644	edit dl rm
copyright	874	0644	edit dl rm
external-reshape-design.txt.gz	4933	0644	edit dl rm
FAQ.gz	11242	0644	edit dl rm
mdmon-design.txt.gz	2561	0644	edit dl rm
NEWS.Debian.gz	2172	0644	edit dl rm
README.checkarray	1667	0644	edit dl rm
README.recipes.gz	1977	0644	edit dl rm
TODO.Debian	1238	0644	edit dl rm
TODO.gz	3097	0644	edit dl rm

Edit: /usr/share/doc/mdadm/TODO.Debian (1238B)

debian mdadm TODO list
======================

- version-1 is a nightmare. E.g. on partitionable arrays, with / on
  /dev/md_d0p3, mdadm -Es ignores /dev/md_d0 and just uses the name, so
  /dev/md/<arrayname>.
- figure out something about device names.
- (better) udev integration

- check whether mdadm.conf and system are consistent during initramfs creation
  and fail otherwise (#381303).
- add code to compare existing and expected configuration, after standardising
  the files. In most cases, we'll have to answer DUNNO as to whether the
  existing configuration file is okay, but I guess in some cases we can
  determine that the configuration is okay. A conservative approach would be
  beneficial to the user. Not sure if it's worth the effort though.
- one nice^W important thing would be to check device names and UUIDs at least.

- verify operation without udev
  - udev removed before mdadm installed
  - udev removed after mdadm installed

- more granular handling of init.d starts/stops, don't force all arrays to be
  started.
- let user specify when to start/stop which array (#398310).
- also only stop those array we started; this can be easily done with
  sentinels in $STATEDIR

- manage DAEMON_OPTIONS with debconf

cmd: