summaryrefslogtreecommitdiffstats
path: root/ChangeLog
Commit message (Collapse)AuthorAgeFilesLines
* Release mdadm-3.1.1NeilBrown2009-11-191-0/+9
| | | | bugfix over 3.1, but changes to some significant defaults.
* Release 3.1NeilBrown2009-10-221-0/+10
| | | | | | New functionality in --grow. Signed-off-by: NeilBrown <neilb@suse.de>
* Release 3.0.3NeilBrown2009-10-221-0/+12
| | | | Signed-off-by: NeilBrown <neilb@suse.de>
* Release mdadm-3.0.2NeilBrown2009-09-251-0/+4
| | | | Just one bugfix.
* Release mdadm-3.0.1NeilBrown2009-09-251-1/+6
| | | | | | Just bugfixes. Signed-off-by: NeilBrown <neilb@suse.de>
* Release mdadm-3.0devel-3.0NeilBrown2009-06-021-770/+11
| | | | | | | | - remove lot of old 'ANNOUNCE' files - trim changelog - update version numbers Signed-off-by: NeilBrown <neilb@suse.de>
* Allow WRITEMOSTLY to be cleared on --readd using --readwrite.NeilBrown2008-10-251-0/+4
| | | | | | | | Previously it was possible to set the WRITEMOSTLY flag when adding a device to an array, but not to clear the flag when re-adding. This is now possible with --readwrite. Signed-off-by: NeilBrown <neilb@suse.de>
* Release 2.6.7mdadm-2.6.7Neil Brown2008-06-061-0/+5
|
* Release 2.6.6mdadm-2.6.6Neil Brown2008-05-191-0/+5
|
* Release 2.6.5mdadm-2.6.5Neil Brown2008-05-151-1/+1
|
* Get Changelog uptodateNeil Brown2008-05-151-0/+8
|
* Allow creation of a RAID6 with a single missing device.Neil Brown2008-04-281-0/+1
| | | | | | | | This did not work before as we couldn't mark it clean as there would be some parity blocks out of sync, and raid6 will not assemble a dirty degraded array. So make such arrays doubly degraded (the last device becomes a spare) and clean.
* Updates some URLs in the man page.Neil Brown2008-04-281-0/+1
| | | | Particularly, add the wiki on osdl.org
* Print 'Events' more sensibly.Neil Brown2008-04-281-0/+2
| | | | Instead of MSW.LSW, just print it as a 64bit number.
* Fix problems with array.size overflowing on large arrays.Neil Brown2008-04-281-0/+2
| | | | | | | | | | | array.size is 32bits and counts K. So for arrays with more than 4Terrabytes, it can overflow. The correct number can be read from sysfs, but there are still a few places that use array.size and risk truncation. What is worse. they compare a number of kilobytes with a number of sectors !! So use get_component_size() to read the sysfs information, and be more consistent about units.
* Fix for segfault when reading /proc/mdstatNeil Brown2008-04-281-0/+4
| | | | | | | | | Some kernel versions don't put a space between 'active' and '(auto-read-only)' in /proc/mdstat. This causes a parsing problem leaving 'level' set to NULL which causes a crash. So synthesise a space there if it is missing, and check for 'level' to be NULL and don't de-ref if it is.
* Release 2.6.4mdadm-2.6.4Neil Brown2007-10-191-0/+7
|
* Release 2.6.3mdadm-2.6.3Neil Brown2007-08-201-1/+1
|
* Update changelogNeil Brown2007-08-201-0/+9
|
* Report error when grow cannot be restarted.Neil Brown2007-08-201-0/+3
| | | | | | Make sure that if --assemble find an array in the critical region of a reshape, and cannot find the critical data to restart the reshape, it gives an error message.
* Fix error message when adding a device that is too small.Neil Brown2007-08-201-0/+2
| | | | | We were multiplying MD_RESERVED_SECTORS by 1024 instead of 512, so lots of 'is it too small' checks were wrong.
* Fix problem with add a device to a 1.x array created with older mdadm.Neil Brown2007-08-201-0/+3
| | | | | | When adding new disk to an array, don't reserve so much bitmap space that the disk cannot store the required data. (Needed when 1.x array was created with older mdadm).
* Allow "--write-behind=" to be done in grow mode.Ian Dall2007-07-091-0/+3
| | | | | | | | | From: Ian Dall <ian@beware.dropbear.id.au> I have a small patch to mdadm which allows the write-behind amount to be set a array grow time (instead of currently only at grow or create time). I have tested this fairly extensively on some arrays built out of loop back devices, and once on a real live array.
* Release 2.6.2mdadm-2.6.2Neil Brown2007-05-211-1/+1
|
* Make return code for "--detail --test" more reliable.Neil Brown2007-05-211-0/+2
| | | | Missing devices as well as failed devices cause an error.
* Add --auto-detect for in-kernel autodetect.Neil Brown2007-05-211-0/+1
| | | | This is equivalent to raidautorun that some distros provide.
* Fix --grow --add for linear arrays.Neil Brown2007-05-211-0/+1
| | | | | | | | | | | | | The new superblock needs to have a new disk.number. This is a bit of a hack... Fix handling of negative bitmap offsets on 64bit hosts. The bitmap offset is a signed 32bit number, so casting to (long) isn't sufficient. We must cast to (int32_t). Fix various problems with --grow --add for linear. The code to add a drive to a live linear array had never been tested properly and so was buggy. This tidies it up and means that the new regression-test passes.
* Support failing and removed of detached and faulty devices.Neil Brown2007-05-111-0/+9
| | | | | This if you unplug a device and udev removes the entry from /dev, you can still remove the device.
* Release 2.6.1mdadm-2.6.1Neil Brown2007-02-221-1/+1
|
* Fixed old documentation in --grow --helpNeil Brown2007-02-221-0/+1
|
* Teach restripe to calculate Q syndrome for raid6.Neil Brown2007-02-221-0/+3
| | | | | This allows mdadm to correctly restart a raid6 grow that crashed during the critcal phase.
* Fix a warning about an uninitialised variable.Neil Brown2007-02-221-0/+1
| | | | | The case that doesn't initialise it is impossible, so just return with an error..
* Fix a bug that was causing incorrect warning from --monitor.Neil Brown2007-02-221-0/+3
|
* Release 2.6mdadm-2.6Neil Brown2006-12-211-1/+1
|
* Add new mode: --incrementalNeil Brown2006-12-211-0/+2
| | | | | --incremental allows arrays to be assembled one device at a time. This is expected to be used with udev.
* Support --uuid= with --create to choose your own UUID.Neil Brown2006-12-141-0/+1
|
* Don't hold md device open for so long in --monitor modeNeil Brown2006-12-141-0/+2
| | | | map_dev can be slow and interferes with trying to stop the array.
* Check device is large enough before hot-add.Neil Brown2006-12-141-0/+2
| | | | This improves quality of error message.
* Change handling for "--assemble --force" when two drives disappeared at once.Neil Brown2006-12-141-0/+3
| | | | | | If two drives in a raid5 disappear at the same time, then "-Af" will add them both in rather than just one and forcing the array to 'clean'. This is slightly safer in some cases.
* Fix and test --update=uuidNeil Brown2006-12-141-0/+1
| | | | A number of odd bugs here, but now we have a regression test as well.
* --wait or -W will wait for resync activity to finish on the given devices.Neil Brown2006-12-141-0/+2
|
* Change 'Device Size' to 'Used Dev Size'Neil Brown2006-12-141-0/+2
| | | | | because it only shows how much of each device is actually used, not how big they are.
* Increase raid456 stripe cache size if needed to --grow the array.Neil Brown2006-12-141-0/+3
| | | | | The setting used unfortunately requires intimate knowledge of the kernel, and it not reset when the reshape finishes.
* Give useful message if raid4/5/6 cannot be started because it is not clean ↵Neil Brown2006-12-141-0/+2
| | | | and is also degraded.
* Default to --auto=yesNeil Brown2006-12-141-0/+2
| | | | | so the array devices with 'standard' names get created automatically, as this is almost always what is wanted.
* Support --update=devicesize for cases where the underlying device can change ↵Neil Brown2006-12-141-0/+2
| | | | size.
* Make Assemble/Force work on raid6 with 2 missing devices.Neil Brown2006-12-141-0/+4
| | | | | | Previously it onl worked when one missing device. Also split the "force" update_super method into two and it is really serving two functions.
* --update=resync did exactly the wrong thing for version1 metadata.Neil Brown2006-11-131-0/+2
|
* Fixed UUID printing in "--detail --brief" for version1 metadata.Neil Brown2006-11-091-0/+3
|
* Fixed problems that could cause infinitel loop with auto assemble.Neil Brown2006-11-091-0/+2
| | | | | | | | | If an auto-assembly attempt failes because the array cannot be opened or because the array has already been created, then we get into an infinite loop. Reported-by: Dan Pascu <dan@ag-projects.com> Fixes-debian-bug: 396582
generated by cgit (git 2.34.1) at 2024-05-01 03:11:55 +0000