summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
* releasing 3.2.2-2Michael Tokarev2012-01-18
|
* add myself to uploadersMichael Tokarev2012-01-18
|
* remove dh_testroot from clean targetMichael Tokarev2012-01-11
|
* (internal) move files from contrib/* topgit branches into debian directoryMichael Tokarev2012-01-11
|
* move all files from contrib/docs/ topgit branches to debian/docs/Michael Tokarev2012-01-11
|
* move mdadd.sh from topgit branch to debian/Michael Tokarev2012-01-11
|
* small changes for debian/checkarrayMichael Tokarev2012-01-10
| | | | | | remove usage of $SYNC_ACTION_CTL in favour of $MDBASE/sync_action since $MDBASE is (and will be) used in other places. While at it, replace var=$(cat foo) with read var < foo construct
* set nice value of the check/resync thread too, together with I/O scheduling ↵Michael Tokarev2012-01-10
| | | | class (Closes: #652547)
* Added support for "status" action to mdadm init script (Closes: #651737)Michael Tokarev2012-01-10
|
* added Slovak (sk.po) po-debconf translation from Slavko (Closes: #641972)Michael Tokarev2012-01-10
|
* mention closing of #633880 too (upstream 3.2.3)Michael Tokarev2012-01-10
|
* fixed a typo (RAID6 vs RAID10) in FAQ (Closes: #637068)Michael Tokarev2012-01-10
|
* update mdadd.sh to version 1.52 (Closes: #655212)Michael Tokarev2012-01-10
|
* update Neil's email (Closes: #650630)Michael Tokarev2012-01-10
|
* updated to new upstream release 3.2.3Michael Tokarev2012-01-10
|
* Merge commit 'mdadm-3.2.3'Michael Tokarev2012-01-10
|\
| * Release mdadm-3.2.3NeilBrown2011-12-23
| | | | | | | | Bug fix release.
| * Grow/bitmap: support adding bitmap via sysfs.NeilBrown2011-12-23
| | | | | | | | | | | | | | | | | | | | Adding a bitmap via ioctl can only add it at a fixed location. That location is not suitable for 4K-block devices. So allow setting the bitmap location via sysfs if kernel supports it and aim to always use 4K alignments. Signed-off-by: NeilBrown <neilb@suse.de>
| * super1: use awrite when writing a new bitmap.NeilBrown2011-12-23
| | | | | | | | | | | | This ensures it will succeed on 4K block devices like DASD. Signed-off-by: NeilBrown <neilb@suse.de>
| * Subject: bitmap: used 4K aligned buffers when reading the bitmap.NeilBrown2011-12-23
| | | | | | | | | | | | | | | | | | This is needed on 4K block devices such as DASD as we do O_DIRECT reads. Do the same alignment for gpt just to be safe. Signed-off-by: NeilBrown <neilb@suse.de>
| * super1 - fix for bigendian machines.NeilBrown2011-12-23
| | | | | | | | | | | | devflags is a single byte so endian conversions are now wanted. Signed-off-by: NeilBrown <neilb@suse.de>
| * Assemble: fix count in "assembled with .. but not started".NeilBrown2011-12-23
| | | | | | | | | | | | We need to include the count of pre-existing devices here. Signed-off-by: NeilBrown <neilb@suse.de>
| * Assemble: make some plurals conditional.NeilBrown2011-12-23
| | | | | | | | | | | | "1 devices" is ugly. Fix it. Signed-off-by: NeilBrown <neilb@suse.de>
| * Incremental: make sure container name appears in /devNeilBrown2011-12-23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We need to send a "change" event just like we do when creating an array. This reverts commit 382afe49b10cf3e5a4764cee74649d1cd8c91813 The problem is that we need udev to create the file in /dev for us. It might be unnecessary for udev to consider assembling things in this array, but it shouldn't cause a problem. If it did that would be a different bug which we probably need locking to fix. Or maybe udev shouldn't trigger a "-I" for containers appearing. Signed-off-by: NeilBrown <neilb@suse.de>
| * bitmap: print correct percentage of bitmap in use.NeilBrown2011-12-23
| | | | | | | | | | | | | | | | We were adding 1, presumably to avoid div-by-zero possibilities. It is better to only substitute '1' if the value actually is zero, else for small numbers of bits the difference is visible. Signed-off-by: NeilBrown <neilb@suse.de>
| * ddf: fix auto-allocation problem.NeilBrown2011-12-23
| | | | | | | | | | | | | | We need to check every disk to see if it has a particular amount of space spare, not just every subsequent disk. Signed-off-by: NeilBrown <neilb@suse.de>
| * allow --monitor to be run by non-privileged use.NeilBrown2011-12-23
| | | | | | | | | | | | | | | | | | | | | | | | Providing --no-sharing is given, monitoring should be permitted. Unfortunately the kernel current rejects GET_DISK_INFO and GET_ARRAY_INFO for non-privileged users which is unjustified. The info is available in sysfs and we could get it from there, but for now, require the kernel to be fixed. Reported-by: Raphael Hertzog <hertzog@debian.org> Signed-off-by: NeilBrown <neilb@suse.de>
| * FIX: Verify if array name doesn't exist alreadyAdam Kwolek2011-12-23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When e.g. array name (an) is correct and it is the same as container name (cn), file element creation /dev/md/an will replace /dev/md/cn. This can cause that user cannot access container using /dev/md/cn. Verify during array creation if chosen name is not already existing one. [Changed to use map_by_name() rather than stat() to determine prior existence - NeilBrown] Signed-off-by: Adam Kwolek <adam.kwolek@intel.com> Signed-off-by: NeilBrown <neilb@suse.de>
| * Grow.c: fix lots of white-space issues.NeilBrown2011-12-23
| | | | | | | | Signed-off-by: NeilBrown <neilb@suse.de>
| * Grow: fix reshape-array for shrinking reshapes.NeilBrown2011-12-23
| | | | | | | | | | | | | | | | | | | | | | The value in info->array.raid_disks is the total number of devices, which is the 'after' number when the number is increasing, and the 'before' number when the number is decreasing. The code currently assumes it is always the 'after' number - so fix that. Signed-off-by: NeilBrown <neilb@suse.de>
| * Grow: fix start_reshape for shrinking arrays.NeilBrown2011-12-23
| | | | | | | | | | | | | | | | | | When an array is being reshaped to fewer data devices the relationship between sync_max and reshape_progress is different to when the number of devices increases - we need to allow for that when setting sync_max/sync_min. Signed-off-by: NeilBrown <neilb@suse.de>
| * tests/03r5assemV1 - slow down recovery a bit more.NeilBrown2011-12-23
| | | | | | | | | | | | | | | | | | | | In this test we stop and restart an array that is being recovered, and we do that several times. Sometimes it completes the recovery before we expect and test results are wrong. So slow it down a bit more. Signed-off-by: NeilBrown <neilb@suse.de>
| * super1: getinfo_super should set write-mostly flag.NeilBrown2011-12-20
| | | | | | | | | | | | | | Otherwise it is not preserved when you re-add a device to an array. Signed-off-by: NeilBrown <neilb@suse.de>
| * imsm: make messages more understandableLukasz Dorau2011-12-20
| | | | | | | | | | | | | | | | | | | | | | | | The printed messages should be more appropriate and understandable for user. If maxsize is equal 0, this means there is no free space left on device. If size is greater than maxsize, this means there is not enough space to create a new volume of given size. Acked-by: Dan Williams <dan.j.williams@intel.com> Acked-by: Marcin Labun <marcin.labun@intel.com> Signed-off-by: Lukasz Dorau <lukasz.dorau@intel.com> Signed-off-by: NeilBrown <neilb@suse.de>
| * imsm: FIX: UT '08imsm-overlap' failsWilliams, Dan J2011-12-20
| | | | | | | | | | | | | | | | | | | | Make test for all sub arrays having the same number of devices dependant on the option ROM requirements being checked. 08imsm-overlap disables the OROM check but then fails because this test causes it to. Reported-by: Adam Kwolek <adam.kwolek@intel.com> Signed-off-by: NeilBrown <neilb@suse.de>
| * Remove update_privateNeilBrown2011-12-20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This fields doesn't work any more as ->getinfo_super clears the info structure at an awkward time. So get rid of it and do it differently. The issue is that the metadata handler cannot tell if the uuid it has was randomly generated or explicitly requested, except on the first call. And we don't want to accept explicit requests for IMSM. So when it was auto-generated, make it look distinctive by having the same int copied in all 4 positions. If someone requests a uuid like that, I guess they get away with it. Reported-by: Adam Kwolek <adam.kwolek@intel.com> Signed-off-by: NeilBrown <neilb@suse.de>
| * imsm: FIX: Chunk size migration is not possibleAdam Kwolek2011-12-15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Chunk size only migration for raid0 and raid5 is not possible. (mdadm UT 15* fails). Mdadm exits with information: mdadm: imsm unknown layout 0xffffffff for this raid level 0 Problem was introduced in patch (2011-11-16): imsm: platform capabilities are not validated during level migration During chunk size migration layout variable is not set correctly. Set it correctly for this migration type. Signed-off-by: Adam Kwolek <adam.kwolek@intel.com> Signed-off-by: NeilBrown <neilb@suse.de>
| * imsm: FIX: return correct status from load_imsm_migr_rec()Adam Kwolek2011-12-15
| | | | | | | | | | | | | | | | | | | | | | | | load_imsm_migr_rec() should see difference between no migration record due to no migration in progress and loading migration record error. Additional return value (-2) was introduced to this function. Using new status load_super_imsm_all() can correctly check loading migration record status. Signed-off-by: Adam Kwolek <adam.kwolek@intel.com> Signed-off-by: NeilBrown <neilb@suse.de>
| * FIX: Add error message in container_reshape()Adam Kwolek2011-12-15
| | | | | | | | | | | | | | | | | | Add proper error message for container reshape when device cannot be opened. fd variable operation is moved down to display information what particular device cannot be opened. Signed-off-by: Adam Kwolek <adam.kwolek@intel.com> Signed-off-by: NeilBrown <neilb@suse.de>
| * FIX: Do not allow for multiple reshape_array() execution during ↵Adam Kwolek2011-12-15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | reshape_container() call It can happen during reshape restart that reshape_array() can exit without error (e.g. Grow.c:1915) and reshape is not moved to next array. reshape_array() is called again for the same device. Do not allow for such execution and check if last reshaped array is not the current one. This patch can be treat not as solution, but it allows for such errors detection. Signed-off-by: Adam Kwolek <adam.kwolek@intel.com> Signed-off-by: NeilBrown <neilb@suse.de>
| * Resolve some more warningsNeilBrown2011-12-13
| | | | | | | | | | | | unused variables when MDASSEMBLE is defined, and a typo in mdadm.8 Signed-off-by: NeilBrown <neilb@suse.de>
| * imsm: FIX: Correct make everything and variable initializationAdam Kwolek2011-12-13
| | | | | | | | | | | | | | | | make everything doesn't compile (again) due to not used function warning and uninitialized variable. Signed-off-by: Adam Kwolek <adam.kwolek@intel.com> Signed-off-by: NeilBrown <neilb@suse.de>
| * imsm: FIX: Use definitions for migration record disk operationsAdam Kwolek2011-12-13
| | | | | | | | | | | | | | | | | | | | Add definition: MIGR_REC_BUF_SIZE MIGR_REC_POSITION to super-intel.c and do not use magic numbers Signed-off-by: Adam Kwolek <adam.kwolek@intel.com> Signed-off-by: NeilBrown <neilb@suse.de>
| * imsm: FIX: Use first map only in migration record disk operationsAdam Kwolek2011-12-13
| | | | | | | | | | | | | | | | | | | | | | This patch is addition to patch: "imsm: FIX: Limit migration record operation by disk slot not by index" Location of migration record (2 first slots) should be taken on up to date information. It is in first map. Change slot verification to use first map only. Signed-off-by: Adam Kwolek <adam.kwolek@intel.com> Signed-off-by: NeilBrown <neilb@suse.de>
| * imsm: FIX: Limit migration record operation by disk slot not by indexAdam Kwolek2011-12-13
| | | | | | | | | | | | | | | | | | imsm should store migration record in to 2 first disks in array. This should be evaluated based on disk slots, not on disks index. It is not guaranteed that indexes are equal to slots. Signed-off-by: Adam Kwolek <adam.kwolek@intel.com> Signed-off-by: NeilBrown <neilb@suse.de>
| * imsm: FIX: Use defines for device map accessAdam Kwolek2011-12-08
| | | | | | | | | | | | | | | | | | | | Maps should not be accessed using "magic numbers" /0, 1,-1/. Add proper definitions and change all map access to use them. Change present definitions /MAP_0/MAP_1/ to values already used in code /0, 1, -1// Signed-off-by: Adam Kwolek <adam.kwolek@intel.com> Signed-off-by: NeilBrown <neilb@suse.de>
| * imsm: FIX: Check correct slots on disk failureAdam Kwolek2011-12-08
| | | | | | | | | | | | | | | | When changes are made to 2nd map, slot in second map should be tested instead first one /as change will be applied to second map). Signed-off-by: Adam Kwolek <adam.kwolek@intel.com> Signed-off-by: NeilBrown <neilb@suse.de>
| * imsm: FIX: Finish rebuild and initialization when missing drive is handledAdam Kwolek2011-12-08
| | | | | | | | | | | | | | | | | | | | | | | | When missing device is handled for rebuild or initialization end_migration() should be called to merge ords in case additional degradation. I've removed this call to end_migration() as it was called for migration also. Signed-off-by: Adam Kwolek <adam.kwolek@intel.com> Signed-off-by: NeilBrown <neilb@suse.de>
| * imsm: FIX: Mark failure for rebuildAdam Kwolek2011-12-08
| | | | | | | | | | | | | | | | Allow for marking failures in second map during rebuild and initialization also (not during migration only) Signed-off-by: Adam Kwolek <adam.kwolek@intel.com> Signed-off-by: NeilBrown <neilb@suse.de>
| * imsm: FIX: Add array map state transition for failures during initializationAdam Kwolek2011-12-08
| | | | | | | | | | | | | | | | During initialization disk failure can occur also. Add code for such case in imsm_set_disk() to support such event. Signed-off-by: Adam Kwolek <adam.kwolek@intel.com> Signed-off-by: NeilBrown <neilb@suse.de>
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-29 05:45:24 +0000