summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Release 2.6mdadm-2.6Neil Brown2006-12-2110-9/+93
|
* Add new mode: --incrementalNeil Brown2006-12-2120-15/+1468
| | | | | --incremental allows arrays to be assembled one device at a time. This is expected to be used with udev.
* Centralise code for copying uuidNeil Brown2006-12-144-38/+25
| | | | Rather than opencoding the byteswap all the time.
* Support --uuid= with --create to choose your own UUID.Neil Brown2006-12-148-24/+59
|
* Fix bug where v1 superblock might appear active when they should be clean.Neil Brown2006-12-142-2/+4
| | | | Only happens on kernel with 32 bit sector_t.
* Central calls to ioctl BLKGETSIZENeil Brown2006-12-1412-141/+62
| | | | Instead of opencoding the same thing everywhere.
* Don't hold md device open for so long in --monitor modeNeil Brown2006-12-142-4/+22
| | | | map_dev can be slow and interferes with trying to stop the array.
* Check device is large enough before hot-add.Neil Brown2006-12-142-1/+37
| | | | This improves quality of error message.
* Change handling for "--assemble --force" when two drives disappeared at once.Neil Brown2006-12-142-1/+24
| | | | | | 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-147-15/+140
| | | | A number of odd bugs here, but now we have a regression test as well.
* When resync finished, report the mismatch count if there is one.Neil Brown2006-12-144-4/+28
| | | | | This doesn't get mailed out, but will appear in syslog... Maybe it should be mailed if it was a 'check' or 'repair' pass...
* --wait or -W will wait for resync activity to finish on the given devices.Neil Brown2006-12-146-3/+55
|
* Change 'Device Size' to 'Used Dev Size'Neil Brown2006-12-144-5/+13
| | | | | 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-144-2/+29
| | | | | 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-146-7/+42
| | | | and is also degraded.
* Default to --auto=yesNeil Brown2006-12-144-14/+19
| | | | | so the array devices with 'standard' names get created automatically, as this is almost always what is wanted.
* Fix a misleading comment.Neil Brown2006-12-141-1/+3
|
* Support --update=devicesize for cases where the underlying device can change ↵Neil Brown2006-12-144-7/+52
| | | | size.
* Improve allocation and use of space for bitmaps in version1 metadataNeil Brown2006-12-145-34/+114
| | | | | | | | | | Depending on the size of the array we reserve space for up to 128K of bitmap, and we use it where possible. When hot-adding to a version 1.0 we can still only use the 3K at the end though - need a sysfs interface to improve that. If a small chunksize is requested on Create, we don't auto-enlarge the reserved space - this still needs to be fixed.
* Actually support --syslogNeil Brown2006-12-141-0/+1
| | | | | | | Fixes-debian-bug: 402457 (part) All the code is there, and it works for '-y', but for some reason, "syslog" was missing from the long_options.
* Remove some unused interfaces to the metadata handlers.Neil Brown2006-12-143-38/+0
| | | | | This stuff has never been used (at least as far as git history can see). I wonder why it was there...
* Make Assemble/Force work on raid6 with 2 missing devices.Neil Brown2006-12-145-7/+29
| | | | | | 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-132-1/+3
|
* Fixed UUID printing in "--detail --brief" for version1 metadata.Neil Brown2006-11-092-1/+4
|
* Release 2.5.6mdadm-2.5.6Neil Brown2006-11-096-23/+56
|
* Fixed problems that could cause infinitel loop with auto assemble.Neil Brown2006-11-092-3/+21
| | | | | | | | | 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
* Document that the default metadata version can be overridden in config file.Goswin Brederlow2006-11-092-0/+7
| | | | | | | | | From: Goswin Brederlow <brederlo@informatik.uni-tuebingen.de> This is already mentioned in the config documentation, but not in the place when the normal default is mentioned. Fixes-debian-bug: 396914
* Strdup the bitmap file name found in the config fileNeil Brown2006-11-092-1/+5
| | | | Otherwise we quickly lose it...
* Release 2-5-5mdadm-2.5.5Neil Brown2006-11-037-5/+49
|
* Support --examine --brief --verbose properlyNeil Brown2006-10-231-0/+2
| | | | | Similar to -Esv, this combination should print out the 'devices=' line in the otherwise --breif output.
* Check error return on a couple of syscalls.Michael Labuschke2006-10-231-3/+6
| | | | From: "Michael Labuschke" <michael@labuschke.de>
* Update test scripts for new blockdevNeil Brown2006-10-232-6/+6
| | | | --getsize64 seems to have disappeared.
* Improve error message when wrong --update option is given.Neil Brown2006-10-233-3/+10
|
* Increase default size of bitmap for v1 superblocks.Neil Brown2006-10-191-1/+1
| | | | | It can be increased further, but that takes a bit more code so will wait for 2.6.
* Fix bugs related to raid10 and the new offset layout.Neil Brown2006-10-193-2/+3
| | | | | Need to mask of bits above the bottom 16 when calculating number of copies.
* Fix array-subscript error.Neil Brown2006-10-191-1/+1
| | | | | ->name is sized to '33' to have room for a trailing nul, but thhat needs to get put in position '32'. Doh!
* Don't trigger and error on -As if all arrays are already started.Luca Berra2006-10-162-1/+3
| | | | | | | From: Luca Berra <bluca@comedia.it> Put another way, if we find any active arrays, then assume things are going as planned.
* Don't fail md_open if array already active.Luca Berra2006-10-162-12/+6
| | | | | | From: Luca Berra <bluca@comedia.it> There is no need and it causes occasional problems.
* Mdassemble improvementsLuca Berra2006-10-166-9/+29
| | | | | | | | | From: Luca Berra <bluca@comedia.it> - Fix a bug where mdassemble didn't close a filedescriptor and so couldn't assembele stacked arrays. - Allow mdassemble, when run a second time, to mark all arrays as writable. This is useful if they are started read-only as is best at boot-time.
* Reduce max bitmap size when bitmap is in a file.Neil Brown2006-10-162-3/+7
| | | | To ensure kernel never needs to allocate more than 1 page contiguously.
* Flush bitmap file before truncate.Neil Brown2006-10-161-0/+1
| | | | | Otheriwse the last write happens on fclose which is after ftruncate, to the truncate has no effect.
* Don't #include blkpg.hNeil Brown2006-10-162-1/+37
| | | | Just include the content directly. It is safer.
* Release 2-5-4mdadm-2.5.4Neil Brown2006-10-136-4/+43
|
* Remove partitions from components of an md arrayNeil Brown2006-10-136-0/+31
| | | | They do nothing but cause confusion.
* Allow a number after --auto=yesNeil Brown2006-10-132-0/+4
| | | | | | So if the device name is /dev/md/d0, then the number of partitions is as given. This is useful in 'CREATE' in mdadm.conf
* Improve the message when mdadm detects similar superblocksNeil Brown2006-10-101-3/+6
| | | | | | | | If they are for a partition and a whole device (common case) they old message doesn't really cover the situation. So add the "overlap" option to the text. Also detect whether the device list was in mdadm.conf and act accordingly.
* Clarify when update=super-minor happens automatciallyNeil Brown2006-10-101-2/+9
| | | | .. in man page
* Fix typo in earlier patch.Neil Brown2006-10-101-1/+1
| | | | Thanks Martin Krafft
* Fixed endian problem with bitmap metdataPaul Clements2006-10-092-0/+2
| | | | From: Paul Clements <paul.clements@steeleye.com>
* Fix some endian-ness issues with v1 superblocks.Neil Brown2006-10-092-9/+19
|