| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
Yes, we do want to free the buf, and the space too if it is still
there.
|
|
|
|
|
|
| |
For arrays that don't have redundancy (raid0, linear etc), the
clean/dirty distinction doesn't mean anything. So always
'assume clean' for these arrays.
|
|\
| |
| |
| | |
git://git.kernel.org/pub/scm/linux/kernel/git/djbw/mdadm into devel-3.0
|
| |
| |
| |
| |
| |
| |
| | |
for development only as console output can block leading to monitor deadlocks
in low mem situations
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
|
|\|
| |
| |
| | |
git://git.kernel.org/pub/scm/linux/kernel/git/djbw/mdadm into devel-3.0
|
| |
| |
| |
| | |
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
|
| |
| |
| |
| | |
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
|
| |
| |
| |
| |
| |
| | |
Ensure that newly written anchors reflect a consistent metadata block.
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
|
| |
| |
| |
| | |
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
A spare device by definition will have raid_disk set to -1, but when
assembling the container we want this disk to by included.
Fixes a SIGSEGV when doing:
mdadm -A /dev/imsm -e imsm /dev/sd[b-e]
...where /dev/sde is marked as a global spare device
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
|
| |
| |
| |
| | |
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
|
| |
| |
| |
| | |
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
|
| |
| |
| |
| |
| |
| |
| | |
It is used later by container_content_imsm to determine set the
text_version of the member arrays.
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
|
| |
| |
| |
| |
| |
| | |
Break out sector_count() for use elsewhere.
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
|
| |
| |
| |
| |
| |
| | |
imsm records this information in its metadata
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
|
| |
| |
| |
| |
| |
| | |
imsm records and validates this data in its metadata
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
|
| |
| |
| |
| | |
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
|
| |
| |
| |
| |
| |
| | |
hostname[17] = 0 overwrites the last byte of the ddf pointer
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
|
| |
| |
| |
| | |
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
|
|\ \
| |/
|/|
| |
| |
| | |
Conflicts:
Makefile
|
| |
| |
| |
| |
| |
| |
| | |
From: Chris Webb <chris@arachsys.com>
We are loading into the already-loaded 'st' instead of the
newly create 'tst', which is clearly wrong.
|
| |
| |
| |
| |
| |
| | |
It is important that dup_super always returns an 'st' with the same
->ss and ->minor_version as the st that was passed.
This wasn't happening for 0.91 metadata (i.e. in the middle of a reshape).
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
Since we made free_super a superswitch call, we need to be careful
that st is non NULL before calling st->ss->free_super(st).
Also when updating byteorder there is a chance of a similar NULL
deref.
|
| |
| |
| |
| | |
Causes compile error with gcc-2.95
|
| |
| |
| |
| |
| |
| |
| |
| | |
If you have stacked arrays, then
mdadm -As --homehost=fred
should work but doesn't. It gets into an infinite loop!
So write some tests, and fix the bugs.
|
| | |
|
| |
| |
| |
| |
| |
| | |
From: David Greaves <david@dgreaves.com>
Signed-off-by: David Greaves <david@dgreaves.com>
|
| |
| |
| |
| | |
and tidy up Makefile a bit.
|
| |
| |
| |
| |
| |
| |
| | |
This is
make MDASSEMBLE_AUTO=1 mdassemble.static
so we now find compile bugs more easily.
|
| | |
|
| |
| |
| |
| | |
Plus various bug fixes etc.
|
| |
| |
| |
| |
| | |
When signalled by the monitor, the manager will find spares and
add them to the array and initiate a recovery.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
Code in manager can now just call queue_metadata_update with a
(freeable) buf holding the update, and it will get passed to the
monitor and written out.
|
| | |
|
| |
| |
| |
| |
| | |
Rather than having to pull them from inside structures and
be_to_cpu them all the time.
|
| |
| |
| |
| |
| | |
i.e. if the add fails, don't add the device to the internal data
structures.
|
| | |
|
| |
| |
| |
| | |
This give more flexability.
|
| |
| |
| |
| |
| |
| | |
'container_member' isn't really a well defined concept.
Each metadata might enumerate members differently, so just
let each format /mdX/YYYY as appropriate.
|
| |
| |
| |
| |
| |
| |
| | |
I want the metadata handler to have more control over the 'version',
particularly for arrays which are members of containers.
So discard st->text_version and instead use info->text_version
which getinfo_super can initialise.
|
| |
| |
| |
| | |
DDF needs more fine grained understanding of the array state.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
"sync_complete" just tracks the current resync/recover/check/whatever pass.
"resync_start" tracks which parts of the array are known to be in-sync
(modulo active writes). So it is what we need to use to update the metadata.
Also we cannot call it when the array has stopped, as the value is no longer
available then. We must call it when the resync completes.
Possibly also call it preiodically if the array is quiescent.
|
| | |
|
| |
| |
| |
| | |
.. and other fixes.
|