summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Increase default chunk size to 512KNeilBrown2009-11-1720-41/+51
| | | | | | | | | | | This seems more appropriate for current (and recent) model drives than 64K. 64K is still the default for '--build' as changing that could corrupt data. 64K is also the default rounding for 'linear' on kernels older than 2.6.16. Signed-off-by: NeilBrown <neilb@suse.de>
* Replace all relevant occurrences of -4 with LEVEL_MULTIPATHNeilBrown2009-11-173-7/+7
| | | | | | Also -1 -> LEVEL_LINEAR. Signed-off-by: NeilBrown <neilb@suse.de>
* Assemble/super0: allow non-in-sync devices to be assembled without complaint.NeilBrown2009-11-171-1/+8
| | | | | | | | Other metadata formats already did not worry about whether 'sync' was missing or not. super0 needs that now, but only for 0.91 metadata that is undergoing reshape. Signed-off-by: NeilBrown <neilb@suse.de>
* Assemble: include ACTIVE but not in-sync devices as non-spares.NeilBrown2009-11-174-4/+4
| | | | | | | | | Previously such things did not exist: ACTIVE and SYNC were either both set or both clear. Recent changes with reshape means that a device can be ACTIVE but not yet fully in-sync, so they need to be handled and included in the array as active devices. Signed-off-by: NeilBrown <neilb@suse.de>
* Grow: data_offset is in sectors, offsets[] is in bytes - convertNeilBrown2009-11-161-1/+1
| | | | | | Another missed sectors->bytes conversion. Signed-off-by: NeilBrown <neilb@suse.de>
* Grow: do not allow size changes with other changes.NeilBrown2009-11-062-0/+18
| | | | | | | | | | | A change the reduces the size of an array always happens before any other change. So it can cause data to be lost. By themselves these changes are reversible. But once another change has started, the data would be permanently lost. So recommend data integrity be checked between a size change and any other change. Signed-off-by: NeilBrown <neilb@suse.de>
* Grow: goto release rather than just returnNeilBrown2009-11-061-4/+8
| | | | | | otherwise we exit with the array frozen. Signed-off-by: NeilBrown <neilb@suse.de>
* Grow: restrict to 2.6.32NeilBrown2009-11-061-0/+6
| | | | | | | | | 2.6.31 has a bug which can lead to unsafe reshaping. So only allow a reshape with 2.6.32. When the required fixed get into 2.6.31.y, this can be relaxed slightly Signed-off-by: NeilBrown <neilb@suse.de>
* Grow: use large block count and make sure stripe cache can hold it.NeilBrown2009-11-061-7/+27
| | | | | | | | The bigger the backup is, the fast it goes to some extend. 16Meg is fairly arbitrary Signed-off-by: NeilBrown <neilb@suse.de>
* Grow: get component_size before using it.NeilBrown2009-11-061-4/+5
| | | | | | | | We were using ->component_size while it hadn't been set. This effectively meant that 'blocks' wasn't multiplied by 16 and reshape was even slower than it should have been. Signed-off-by: NeilBrown <neilb@suse.de>
* Grow: handle array going degraded during reshape.NeilBrown2009-11-061-6/+35
| | | | | | | | If an array goes degraded during reshape, we need to adjust the devices we read from so as not to back up stale data. Signed-off-by: NeilBrown <neilb@suse.de>
* Grow: restore backup to proper location.NeilBrown2009-11-061-2/+2
| | | | | | | | | | The 'arraystart' is in sectors while restore_stripes requires bytes, so we need a conversion. Without this, backups get restored to the wrong offset. Reported-by: "KueiHuan Chen" <kueihuan.chen@gmail.com> Signed-off-by: NeilBrown <neilb@suse.de>
* Detail: report new-layout for RAID6 arraysNeilBrown2009-10-291-0/+5
| | | | | | We were only reporting it for RAID5 and RAID10. Signed-off-by: NeilBrown <neilb@suse.de>
* Release 3.1NeilBrown2009-10-228-5/+52
| | | | | | New functionality in --grow. Signed-off-by: NeilBrown <neilb@suse.de>
* Merge branch 'master' into devel-3.1NeilBrown2009-10-228-5/+49
|\
| * Release 3.0.3NeilBrown2009-10-228-5/+49
| | | | | | | | Signed-off-by: NeilBrown <neilb@suse.de>
* | Merge branch 'master' into devel-3.1NeilBrown2009-10-2220-316/+869
|\|
| * Free some malloced memory that wasn't being freed.NeilBrown2009-10-223-2/+8
| | | | | | | | | | | | | | | | | | | | As mdadm is normally a short-lived program it isn't always necessary to free memory that was allocated, as the 'exit()' call will automatically free everything. But it is more obviously correct if the 'free' is there. So this patch add a few calls to 'free' Signed-off-by: NeilBrown <neilb@suse.de>
| * super-intel: Fix compilation of mdassemble.NeilBrown2009-10-201-1/+7
| | | | | | | | Signed-off-by: NeilBrown <neilb@suse.de>
| * testreshape5 fixes.NeilBrown2009-10-201-1/+2
| | | | | | | | | | | | We seem to need a 'udevadm settle', and possibly the 'sync'.. Signed-off-by: NeilBrown <neilb@suse.de>
| * tests/imsm: allow for rounding of array size.NeilBrown2009-10-202-0/+8
| | | | | | | | | | | | | | IMSM rounds array size to a multiple of 1024K, so our tests must assume this. Signed-off-by: NeilBrown <neilb@suse.de>
| * mdopen: only use 'dev' as chosen name if it is a full path.NeilBrown2009-10-191-2/+1
| | | | | | | | | | | | | | Otherwise using names like "r0" causes problem. They are handled sufficiently by other paths in the code. Signed-off-by: NeilBrown <neilb@suse.de>
| * Assemble: handle container members betterNeilBrown2009-10-191-0/+18
| | | | | | | | | | | | | | When looking for a specific member, don't accept a different member, but step on to the next one. Signed-off-by: NeilBrown <neilb@suse.de>
| * Assemble: print verbose messages when finding members in containersNeilBrown2009-10-191-0/+6
| | | | | | | | | | | | .. so that "-Av" gives more hints at what is going on. Signed-off-by: NeilBrown <neilb@suse.de>
| * Detail: list containers before members.NeilBrown2009-10-191-0/+8
| | | | | | | | | | | | | | To allow "--assemble --scan" to have a chance, list containers before members in --detail --scan output. Signed-off-by: NeilBrown <neilb@suse.de>
| * test/ddf: don't insist that mdadm.conf is always in the same order.NeilBrown2009-10-191-4/+4
| | | | | | | | | | | | | | When created by different process, the order could reasonably be different. So sort before compare Signed-off-by: NeilBrown <neilb@suse.de>
| * test/raid6integ: correct typeNeilBrown2009-10-191-2/+2
| | | | | | | | | | | | ddf-zero-restart was misspelled. Signed-off-by: NeilBrown <neilb@suse.de>
| * test: udev-settle before testing device.NeilBrown2009-10-191-0/+1
| | | | | | | | | | | | | | I think we sometime get way ahead of udev and devices disappear and appear almost at random. So add some settling. Signed-off-by: NeilBrown <neilb@suse.de>
| * mdadm(8): fix spurious space after -e headerMike Frysinger2009-10-191-1/+1
| | | | | | | | | | Signed-off-by: Mike Frysinger <vapier@gentoo.org> Signed-off-by: NeilBrown <neilb@suse.de>
| * Monitor: add option to specify rebuild incrementsZdenek Behan2009-10-195-17/+36
| | | | | | | | | | | | | | | | | | | | ie. the percent increments after which RebuildNN event is generated This is particulary useful when using --program option, rather than (only) syslog for alerts. Signed-off-by: Zdenek Behan <rain@matfyz.cz> Signed-off-by: NeilBrown <neilb@suse.de>
| * mdmon: lock current memory as well as future memory.NeilBrown2009-10-191-1/+1
| | | | | | | | | | | | | | | | mlockall(MCL_FUTURE) only locks mappings that have not yet been created. To lock all memory used by the process, we need MCL_CURRENT | MCL_FUTURE Signed-off-by: NeilBrown <neilb@suse.de>
| * Merge git://github.com/djbw/mdadmNeilBrown2009-10-1914-289/+780
| |\
| | * mdmon: preserve socket over chrootDan Williams2009-10-136-12/+26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Connect to the monitor in the old namespace and use that connection for WaitClean requests when stopping the victim mdmon instance. This allows ping_monitor() to work post chroot(). Cc: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Dan Williams <dan.j.williams@intel.com>
| | * mdmon: exec(2) when the switchroot argument is not "/"Dan Williams2009-10-131-0/+23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Try to execute mdmon from the target namespace. When used for initramfs handovers we need to drop all references to the initramfs filesystem for that memory to be freed. Cc: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Dan Williams <dan.j.williams@intel.com>
| | * mdmon: avoid writes in the startup path for mdmon on root arraysDan Williams2009-10-132-46/+38
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When killing a previous monitor be careful not to cause writes to the filesystem until the reads necessary to get the monitor operational have completed. The code is already prepared for errors creating the pid and socket files, so simply defer creation of these files until after the first call to manage(). Cc: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Dan Williams <dan.j.williams@intel.com>
| | * Detail: export MD_UUID from mapfileDan Williams2009-10-133-4/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The load_super() from an mdadm --detail call may race against an mdmon update. When this happens the load_super sees an inconsistent metadata block and returns an error. The fallback path to use the map file contents lacks uuid reporting, so provide __fname_from_uuid for generically printing a uuid. Reported-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Dan Williams <dan.j.williams@intel.com>
| | * imsm: regression test for prodigal array member scenarioDan Williams2009-10-132-0/+78
| | | | | | | | | | | | | | | | | | | | | | | | Provide a test to sanity check assembly and reassembly in the presence of conflicting family number information. Signed-off-by: Dan Williams <dan.j.williams@intel.com>
| | * imsm: add --update=uuid supportDan Williams2009-10-133-12/+47
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When disks have conflicting container memberships (same container ids but incompatible member arrays) --update=uuid can be used to move offenders to a new container id by changing 'orig_family_num'. Note that this only supports random updates of the uuid as the actual uuid is synthesized. We also need to communicate the new 'orig_family_num' value to all disks involved in the update. A new field 'update_private' is added to struct mdinfo to allow this information to be transmitted. Signed-off-by: Dan Williams <dan.j.williams@intel.com>
| | * ddf: prevent superblock being zeroed on --updateDan Williams2009-10-131-8/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The full fix would be to support updating ddf metadata, but this minimal fix just prevents the superblock from being zeroed when someone inadvertently passes an unsupported --update option during assembly. Reported-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Dan Williams <dan.j.williams@intel.com>
| | * imsm: fix/support --updateDan Williams2009-10-131-28/+26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fix init_super_imsm() to return an empty mpb when info == NULL, and teach store_super_imsm() to simply write out the passed in mpb. Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=523320 Reported-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Dan Williams <dan.j.williams@intel.com>
| | * imsm: fix spare record writeout raceDan Williams2009-10-131-24/+35
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | imsm_activate_spare() in the manager thread may race against write_super_imsm_spares() in the monitor thread. Give write_super_imsm_spares() its own private mpb buffer to prevent confusing the manager. This change uncovered cases where spares were not being assembled due to a failed metadata version number check. Spares can freely associate across metadata version number, so reduce the scope of the version check in the spare assembly case. Signed-off-by: Dan Williams <dan.j.williams@intel.com>
| | * imsm: disambiguate family_numDan Williams2009-09-301-132/+448
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is a result of trawling through the Windows implementation to learn the mechanism of how it disambiguates family_num. It is a continuation of commit 148acb7b "imsm: fix family number handling" which introduced a regression when reassembling a container with stale disks and rebuilt members. When rebuilding, a new family number is assigned to protect against the "prodigal array member" problem. It prevents a former family member from returning to the system and causing a rebuild to go the wrong direction. However, this invalidates looking at the generation number to determine the most up-to-date disk when comparing across family numbers. Instead the assembly logic looks for agreement between a disk's local family membership compared against a global list of all families in the system. Whenever a disk's local metadata does not match a family number on the global list that family number is marked offline. It is possible that this logic results in multiple incompatible but valid family numbers existing in a container. In this case mdadm.conf cannot be consulted because it only records the uuid which is generated from static fields in the metadata. The metadata lacks the data needed to disambiguate "local" versus "foreign". The "foreign" array in this case requires updating to change its container-id information (orig_family_num), and possibly the member array names. Signed-off-by: Dan Williams <dan.j.williams@intel.com>
| | * imsm: kill close() of component deviceDan Williams2009-09-301-3/+1
| | | | | | | | | | | | | | | | | | | | | | | | None of the other formats close the passed in fd at load, and this becomes a problem when trying to support --update where we need O_EXCL protection across the entire operation. Signed-off-by: Dan Williams <dan.j.williams@intel.com>
| | * imsm: cleanup disk status testsDan Williams2009-09-281-24/+29
| | | | | | | | | | | | | | | | | | | | | Add is_failed(), is_configured(), and is_spare() helpers to clean up disk status flag testing. Signed-off-by: Dan Williams <dan.j.williams@intel.com>
* | | Grow: update backup-metadata mtime every time we write it.NeilBrown2009-10-221-2/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Originally the backup-metadata was only written once at the start of a raid5 reshape that made the array bigger. So we only set the mtime once. Now that we can be writing metadata continually during an in-place reshape, we need to update the mtime more often. Also, allow the metadata mtime to be slightly in advance of the array mtime. Normally the difference will be less than a second, so 10 minutes should be plenty. This guards against an old backup file being used to restart an array. but starting two reshapes in the 10 minutes is sufficiently unlikely, and the possibility of an accident is already sufficiently small, that 10 minutes is probably fine. Thanks to Guy Martin <gmsoft@tuxicoman.be> for discovering and reporting that .mtime wasn't being updated properly. Signed-off-by: NeilBrown <neilb@suse.de>
* | | Compile fixes for mdassembleNeilBrown2009-10-202-0/+4
| | | | | | | | | | | | Signed-off-by: NeilBrown <neilb@suse.de>
* | | Grow: reject raid-disks reduction in RAID5 etc before 2.6.32NeilBrown2009-10-201-1/+9
| | | | | | | | | | | | | | | | | | | | | 2.6.31 has some bugs with restarting a RAID5 reduction, so refuse to try unless at least 2.6.32. Signed-off-by: NeilBrown <neilb@suse.de>
* | | Assemble: print more verbose messages about restarting a reshapeNeilBrown2009-10-203-20/+63
| | | | | | | | | | | | Signed-off-by: NeilBrown <neilb@suse.de>
* | | Add missing 'continue' in Grow_restart.NeilBrown2009-10-201-0/+1
| | | | | | | | | | | | | | | | | | Thus we weren't checking the uuid properly. Signed-off-by: NeilBrown <neilb@suse.de>
* | | tests/imsm: allow for rounding of array size.NeilBrown2009-10-162-0/+8
| | | | | | | | | | | | | | | | | | | | | IMSM rounds array size to a multiple of 1024K, so our tests must assume this. Signed-off-by: NeilBrown <neilb@suse.de>
generated by cgit (git 2.34.1) at 2024-10-01 06:51:30 +0000