summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
* document last patch buy Sergey and update .po filesMichael Tokarev2012-06-22
|
* Drop unused debconf templatesSergey B Kirpichev2012-06-22
|
* document last patch buy SergeyMichael Tokarev2012-06-22
|
* Fix spelling in binaries, fix lintian warnings manpage-has-errors-from-man ↵Sergey B Kirpichev2012-06-22
| | | | and hyphen-used-as-minus-sign
* fix spelling mistakes in previous changelog entryMichael Tokarev2012-06-22
|
* add changelog entries for patches by Sergey B KirpichevMichael Tokarev2012-06-22
|
* Fix lintian info's conflicts-with-version: Conflicts -> BreaksSergey B Kirpichev2012-06-22
|
* Implement status option for mdadm-raid init.d scriptSergey B Kirpichev2012-06-22
|
* Fix mdadm.lintian-overridesSergey B Kirpichev2012-06-22
|
* releasing 3.2.5-1 to unstableMichael Tokarev2012-05-25
|
* add changelog entries for patches by Dmitrijs LedkovsMichael Tokarev2012-05-25
|
* Remove debian-specific mdadm-startall.8 in clean targetDmitrijs Ledkovs2012-05-25
| | | | | I know that $ git clean -X -f is amazing, but being tidy is still nice.
* Remove compatability with acient initramfs-tools.Dmitrijs Ledkovs2012-05-25
| | | | | | | | | On one hand, it is saver to have it in. On the other hand, people should have transitions to initramfs since etch, and it would be challenging to support acient initrd's. I'd want to see this go...
* Update debconf templates translations.Dmitrijs Ledkovs2012-05-25
| | | | Due to a change introduced in the previous commit.
* Remove reference to obsolete documention from debconf templates.Dmitrijs Ledkovs2012-05-25
| | | | | Please note this change requires updating translation files. See next commit.
* Remove obsolete documentation dating back to ~etch releaseDmitrijs Ledkovs2012-05-25
|
* do not check recently created arrays (#624273)Michael Tokarev2012-05-25
|
* new upstream release, make it compilable tooMichael Tokarev2012-05-25
|
* Merge mdadm-3.2.5 into debianMichael Tokarev2012-05-25
|\
| * Create new release: 3.2.5NeilBrown2012-05-18
| | | | | | | | | | | | | | Fix a serious regression in 3.2.4 which caused "--add" to often fail. Other minor fixes included. Signed-off-by: NeilBrown <neilb@suse.de>
| * Update some device sizes for self tests.NeilBrown2012-05-18
| | | | | | | | | | | | | | | | A recent change means that devices smaller than 1Gig no longer have 1Meg wasted at the start. So we must adjust some sizes again. Signed-off-by: NeilBrown <neilb@suse.de>
| * imsm: fix: check if size of expansion is not larger than maximumLukasz Dorau2012-05-18
| | | | | | | | | | | | | | | | | | | | | | | | | | We do not check if requested size of expansion is larger than maximum available size now. If it is larger the output message is a bit misleading, for example: mdadm: Cannot set size on array members. mdadm: Cannot set device size for /dev/md/vol: Device or resource busy Now we check if requested size of expansion is larger than maximum available size and the appropriate output message was added. Signed-off-by: Lukasz Dorau <lukasz.dorau@intel.com> Signed-off-by: NeilBrown <neilb@suse.de>
| * imsm: fix a typo in fprintf messageLukasz Dorau2012-05-18
| | | | | | | | | | Signed-off-by: Lukasz Dorau <lukasz.dorau@intel.com> Signed-off-by: NeilBrown <neilb@suse.de>
| * mdadm.conf.5: typo: of -> orNeilBrown2012-05-18
| | | | | | | | | | | | Addresses-Debian-bug: 673344 Reported-by: Robert Henney <robh@rut.org> Signed-off-by: NeilBrown <neilb@suse.de>
| * RebuildMap: check that container_content returns a valid 'info'.NeilBrown2012-05-17
| | | | | | | | | | | | | | If it doesn't, just skip that entry. Reported-by: Maciej Naruszewicz <maciej.naruszewicz@intel.com> Signed-off-by: NeilBrown <neilb@suse.de>
| * Don't consider disks with a valid recovery offset as candidates for bumping ↵Alexander Lyakas2012-05-15
| | | | | | | | | | | | | | | | | | | | | | | | up event count When we are looking for a candidate disk to bump up the event count, we consider only disks that have recovery_start==MaxSector. However, after we find one such disk, we agree to accept more disks having same event count, regardless of their recovery_start. Be consistent and don't accept disks with a valid recovery_start at all. Signed-off-by: NeilBrown <neilb@suse.de>
| * Grow: don't print message if unfreezing fails.NeilBrown2012-05-15
| | | | | | | | | | | | | | | | This is most likely to happen if the array has been stopped, in which case the error is pointless. Reported-by: Patrik Horník <patrik@dsl.sk> Signed-off-by: NeilBrown <neilb@suse.de>
| * Grow: fix --layout=preserve to match man page.NeilBrown2012-05-15
| | | | | | | | | | | | | | | | | | | | | | I think there was some confusion about what --layout=preserve actually means, but in any case it wasn't doing what the man page says it should. So add some case analysis and make sure it does the right thing, or complains if it cannot. Reported-by: Patrik Horník <patrik@dsl.sk> Signed-off-by: NeilBrown <neilb@suse.de>
| * super1: fix choice of data_offset.NeilBrown2012-05-15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | While it is nice to set a high data_offset to leave plenty of head room it is much more important to leave enough space to allow of the data of the array. So after we check that sb->size is still available, only reduce the 'reserved', don't increase it. This fixes a bug where --adding a spare fails because it does not have enough space in it. Reported-by: nowhere <nowhere@hakkenden.ath.cx> Signed-off-by: NeilBrown <neilb@suse.de>
| * New sha1.c and sha1.hNeilBrown2012-05-15
| | | | | | | | | | | | | | | | | | | | | | These are from: http://gcc.gnu.org/svn/gcc/branches/cilkplus/include/sha1.h and http://gcc.gnu.org/svn/gcc/branches/cilkplus/libiberty/sha1.c and hopefully avoid aliasing issues. Signed-off-by: NeilBrown <neilb@suse.de>
* | uploading 3.2.4-1 to unstableMichael Tokarev2012-05-10
| |
* | add build-arch and build-indep targets to debian/rules (standards-version: ↵Michael Tokarev2012-05-10
| | | | | | | | 3.9.3)
* | adopt mdadm-3.2.4 upstream releaseMichael Tokarev2012-05-10
| |
* | Merge branch 'upstream' into 'debian'Michael Tokarev2012-05-10
|\| | | | | | | This merges mdadm-3.2.4 upstream into debian branch.
| * Create new release: 3.2.4NeilBrown2012-05-09
| | | | | | | | | | | | Bugfix release Signed-off-by: NeilBrown <neilb@suse.de>
| * super-intel.c: Fix resource leak from opendir()Jes Sorensen2012-05-07
| | | | | | | | | | | | | | | | Use closedir() on dirp from opendir() to avoid resource leaking. Acked-by: Dan Williams <dan.j.williams@intel.com> Signed-off-by: Jes Sorensen <Jes.Sorensen@redhat.com> Signed-off-by: NeilBrown <neilb@suse.de>
| * super-intel.c: Don't try to close negative fdJes Sorensen2012-05-07
| | | | | | | | | | | | | | | | | | This should be harmless, but lets be consistent and not try to close a negative file descripter. Acked-by: Dan Williams <dan.j.williams@intel.com> Signed-off-by: Jes Sorensen <Jes.Sorensen@redhat.com> Signed-off-by: NeilBrown <neilb@suse.de>
| * Grow: failing the set the per-device size is not an error.NeilBrown2012-05-03
| | | | | | | | Signed-off-by: NeilBrown <neilb@suse.de>
| * test: don't worry too much about array size.NeilBrown2012-05-03
| | | | | | | | | | | | | | | | With different amounts of space being reserved for metadata it is hard for the script to know how big the array should be. So allow a bit of slack. Signed-off-by: NeilBrown <neilb@suse.de>
| * Adjust to new standard of /runNeilBrown2012-05-03
| | | | | | | | | | | | | | | | Now that /run seems to be a good standard, make that the default for storing various run-time files, rather than /var/run or /dev/.mdadm. Signed-off-by: NeilBrown <neilb@suse.de>
| * Update test for "is udev active".NeilBrown2012-05-03
| | | | | | | | | | | | | | | | Newer udev doesn't use /dev/.udev any more. it used /run/udev instead. So test for that as well. Signed-off-by: NeilBrown <neilb@suse.de>
| * imsm: fix: thunderdome may drop 2tb attributeCzarnowska, Anna2012-04-30
| | | | | | | | | | | | | | | | | | | | | | | | Spare superblock doesn't depend on other spares in container. When loading container metadata thunderdome may pick a small disk for the champion. This will result in incorrect interpretation of sizes of other disks in container when joint superblock is returned. If any disk in container has the 2TB attribute set, the result must have it set too. Signed-off-by: Anna Czarnowska <anna.czarnowska@intel.com> Signed-off-by: NeilBrown <neilb@suse.de>
| * Introduce sysfs_set_num_signed() and use it to set bitmap/offsetJes Sorensen2012-04-30
| | | | | | | | | | | | | | | | | | | | mdinfo->bitmap_offset is a signed long and needs to be treated as such when passed to the kernel. This resolves the problem with adding internal bitmaps to a 1.0 array. Signed-off-by: Jes Sorensen <Jes.Sorensen@redhat.com> Signed-off-by: NeilBrown <neilb@suse.de>
| * Fix sign extension of bitmap_offset in super1.cJes Sorensen2012-04-30
| | | | | | | | | | | | | | | | | | | | fbdef49811c9e2b54e2064d9af68cfffa77c6e77 incorrectly tried to fix sign extension of the bitmap offset. However mdinfo->bitmap_offset is a u32 and needs to be converted to a 32 bit signed integer before the sign extension. Signed-off-by: Jes Sorensen <Jes.Sorensen@redhat.com> Signed-off-by: NeilBrown <neilb@suse.de>
| * fix: correct extending size of raid0 arrayLukasz Dorau2012-04-23
| | | | | | | | | | | | | | | | | | Setting "sync_action" to "idle" while extending size of raid0 array is racy and sometimes fails. "sync_action" should be set to "frozen" instead. Signed-off-by: Lukasz Dorau <lukasz.dorau@intel.com> Signed-off-by: NeilBrown <neilb@suse.de>
| * imsm: fix: rebuild does not continue after rebootLukasz Dorau2012-04-23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | If system is rebooted during rebuild, md driver changes sync_action from 'recover' to 'idle' (during stopping all md devices). If mdmon is still running then, it detects the change of sync_action state, finishes rebuild and writes metadata to disks. After computer's restart the RAID volume is in Normal state in OROM and rebuild seems to be finished. After system's start-up RAID volume is in auto-read-only state and metadata is in Dirty state. Rebuild seems to be finished but it is not. Data is inconsistent (out-of-sync). When mdmon detects the change of sync_action from 'recover' to 'idle', it has to check if rebuild is really finished. Appropriate test was added. Now mdmon examines each volume's member if it is being rebuilt. Signed-off-by: Lukasz Dorau <lukasz.dorau@intel.com> Signed-off-by: NeilBrown <neilb@suse.de>
| * Relax restrictions on when --add is permitted.NeilBrown2012-04-18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The restriction that --add was not allowed on a device which looked like a recent member of an array was overly harsh. The real requirement was to avoid using --add when the array had failed, and the device being added might contain necessary information which can only be incorporated by stopping and re-assembling with --force. So change the test to reflect the need. Reported-by: Doug Ledford <dledford@redhat.com> Signed-off-by: NeilBrown <neilb@suse.de>
| * Add --prefer option for --detail and --monitorNeilBrown2012-04-18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Both --detail and --monitor can report the names of member devices on an array, and do so by searching /dev and finding the shortest name that matches. If --prefer=foo is given, they will instead prefer a name that contain /foo/. So mdadm --detail /dev/md0 --prefer=by-path will list the component devices via their /dev/disk/by-path/xxx names. Signed-off-by: NeilBrown <neilb@suse.de>
| * Raid limit of 1024 when scanning for devices.NeilBrown2012-04-18
| | | | | | | | | | | | | | | | When we can for devices using GET_DISK_INFO we currently limit to 1024. But some arrays can have more than this. So raise it to 4096 and make the constant a #define. Signed-off-by: NeilBrown <neilb@suse.de>
| * FIX: resolve make everything compilation errorLukasz Dorau2012-04-17
| | | | | | | | | | | | | | | | | | | | When mdadm is compiled using e.g. 'everything' option, mdassemble compilation is broken. Change code to enable mdassemble compilation. Signed-off-by: Lukasz Dorau <lukasz.dorau@intel.com> Signed-off-by: NeilBrown <neilb@suse.de>