| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Signed-off-by: Doug Ledford <dledford@redhat.com>
|
|
|
|
| |
Signed-off-by: Doug Ledford <dledford@redhat.com>
|
|
|
|
| |
Signed-off-by: Doug Ledford <dledford@redhat.com>
|
|
|
|
|
|
| |
IncrementalNewDisk
Signed-off-by: Doug Ledford <dledford@redhat.com>
|
|
|
|
| |
Signed-off-by: Doug Ledford <dledford@redhat.com>
|
|
|
|
|
|
|
| |
stat buffer instead of making callers do a second stat if they need
something from the stat buffer
Signed-off-by: Doug Ledford <dledford@redhat.com>
|
|
|
|
|
|
|
| |
we might need to repartition a device, and one for when we will be
using the block device directly.
Signed-off-by: Doug Ledford <dledford@redhat.com>
|
|
|
|
|
|
| |
sanity checks for us
Signed-off-by: Doug Ledford <dledford@redhat.com>
|
|
|
|
|
|
| |
entry instead of just a program name.
Signed-off-by: Doug Ledford <dledford@redhat.com>
|
|
|
|
|
|
|
| |
layer so we can easily support different partitioning methods required
for different platforms
Signed-off-by: Doug Ledford <dledford@redhat.com>
|
|
|
|
| |
Signed-off-by: Doug Ledford <dledford@redhat.com>
|
|
|
|
|
|
| |
a requirement.
Signed-off-by: Doug Ledford <dledford@redhat.com>
|
|
|
|
|
|
| |
turns out there are no good paths, then do throw the domain away.
Signed-off-by: Doug Ledford <dledford@redhat.com>
|
|
|
|
| |
Signed-off-by: Doug Ledford <dledford@redhat.com>
|
|
|
|
|
|
|
|
| |
just the initial stages. Added support for the call to mdadm.c, some
sanity checks on how we are called, some of the initial easy sanity
checks that kick us out of the new function, etc.
Signed-off-by: Doug Ledford <dledford@redhat.com>
|
|
|
|
|
|
|
|
|
|
| |
This allows us to pull the path information for our current device
and filter the list of possible matching domains based upon that
path information. Since we only support identical partition tables,
if an array is comprised of -part1 partitions already, then we know that
our new device will only match on -part1 as well.
Signed-off-by: Doug Ledford <dledford@redhat.com>
|
|
|
|
| |
Signed-off-by: Doug Ledford <dledford@redhat.com>
|
|
|
|
|
|
| |
symlinks when we've already got our domain
Signed-off-by: Doug Ledford <dledford@redhat.com>
|
|
|
|
| |
Signed-off-by: Doug Ledford <dledford@redhat.com>
|
|
|
|
|
|
|
| |
install new udev early rules, update ReadMe.c for new options to pass
to incremental mode, update udev rules file for new options.
Signed-off-by: Doug Ledford <dledford@redhat.com>
|
|
|
|
| |
Signed-off-by: Doug Ledford <dledford@redhat.com>
|
|
|
|
| |
Signed-off-by: Doug Ledford <dledford@redhat.com>
|
|
|
|
| |
Signed-off-by: Doug Ledford <dledford@redhat.com>
|
|
|
|
|
|
| |
for automatic hot spare/rebuild use.
Signed-off-by: Doug Ledford <dledford@redhat.com>
|
|
|
|
|
|
|
| |
udev hot plug sequence, allowing us to make them our own if they
match a proper DOMAIN entry in the mdadm.conf file
Signed-off-by: Doug Ledford <dledford@redhat.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
in stb.st_rdev to use in ioctl calls. Therefore, even if we use the sysfs
block/dev entry to get our major/minor pair, we should really be using
tfd and not sysfd as it changes assumptions made later on.
Note: I actually don't like this. I would prefer that in the case of a
kernel internal name that we skipped tfd altogether and went strait to
sysfs operation exclusively. But that's just my preference. I'm
concerned that sometime in the future we'll make the mistake of assuming
that tfd >= 0 means dv->devname is a fully qualified path name and not
a kernel internal name. We don't now, but I could easily see it happening.
Signed-off-by: Doug Ledford <dledford@redhat.com>
|
|
|
|
|
|
|
|
| |
well as regular mdadm arrays. Check to see if we were told on the boot
command line to ignore IMSM arrays first though (aka, rd_NO_MDIMSM is not
empty).
Signed-off-by: Doug Ledford <dledford@redhat.com>
|
|
|
|
| |
Signed-off-by: Doug Ledford <dledford@redhat.com>
|
|
|
|
|
|
| |
point
Signed-off-by: Doug Ledford <dledford@redhat.com>
|
|
|
|
| |
Signed-off-by: Doug Ledford <dledford@redhat.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
3 directory definitions: mdmon directory for its pid and sock files,
mdmonitor directory which is for the mdadm monitor mode pid file and
can only be passed in via command line, and the directory for the
mdadm map file. Only the mdadm map file still hunts multiple locations,
and the number of locations has been reduced to /var/run and the
compile time specified location. I could see lowering that to just
1 location, but I didn't do that with this patch.
Signed-off-by: Doug Ledford <dledford@redhat.com>
|
|
|
|
|
|
|
|
|
| |
- split the rules for handling components of array to be clearly
separate from rules for handling the arrays themselves.
- add call to "-If" when removing a device
- uncomment the --incremental call when adding a device.
Signed-off-by: NeilBrown <neilb@suse.de>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This can be used for hot-unplug. When a device has been remove,
udev can call
mdadm --incremental --fail sda
and mdadm will find the array holding sda and remove sda from
the array.
Based on code from Doug Ledford <dledford@redhat.com>
Signed-off-by: NeilBrown <neilb@suse.de>
|
|
|
|
|
|
|
|
|
|
| |
Allow kernel names like "sda" and "hdb1" to be used to
fail/remove devices from an array.
This is useful as after a device has been removed it can be difficult
to get the major/minor number.
Signed-off-by: NeilBrown <neilb@suse.de>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This allows finding the array which contains a given component.
Components are named using the kernel-internal string name such
as "sda1" or "hdb".
Don't return member arrays, only the contain that contains them.
Also tidy up the parsing of 'inactive' arrays in /proc/mdstat.
If we see 'inactive' we need to set 'in_devs' immediately as there
is no level coming.
Signed-off-by: NeilBrown <neilb@suse.de>
|
|
|
|
|
| |
Signed-off-by: Doug Ledford <dledford@redhat.com>
Signed-off-by: NeilBrown <neilb@suse.de>
|
|
|
|
|
|
|
| |
In particular, if the relevant bitmap method is NULL, don't try to
call it, print an error instead.
Signed-off-by: NeilBrown <neilb@suse.de>
|
|\ |
|
| |
| |
| |
| |
| |
| | |
Forgot to git-add this for the release :-(
Signed-off-by: NeilBrown <neil@suse.de>
|
| |
| |
| |
| | |
Signed-off-by: Doug Ledford <dledford@redhat.com>
|
| |
| |
| |
| |
| |
| | |
a custom filename too.
Signed-off-by: Doug Ledford <dledford@redhat.com>
|
| |
| |
| |
| |
| |
| |
| |
| | |
filesystem is writable).
This particularly keeps udev happy if VAR_RUN is set to /dev/md.
Signed-off-by: Doug Ledford <dledford@redhat.com>
Signed-off-by: NeilBrown <neilb@suse.de>
|
|/ |
|
| |
|
|
|
|
|
|
|
| |
Default metadata type is now 1.2, and we sometimes
add extra alignment before the data section,
so adjust tests for these changes.
Signed-off-by: NeilBrown <neilb@suse.de>
|
|
|
|
|
|
|
|
| |
Matching the functionality already in super0 and super1, when
we first create a container, remove any other recognisable metadata to
ensure it doesn't cause confusion.
Signed-off-by: NeilBrown <neilb@suse.de>
|
|
|
|
|
|
|
|
|
| |
Recent fix to check lseek64 return status got it badly wrong.
It doesn't return 0 on success!!
Fix it.
Signed-off-by: NeilBrown <neilb@suse.de>
|
|
|
|
|
|
|
|
| |
Found during testing:
- cannot check metadata for homehost before loading metadata.
- As 1.x metadata can has a state 'rebuilding' between
'spare' and 'ok', we need to include that in our calculations.
Signed-off-by: NeilBrown <neilb@suse.de>
|
|\ |
|
| |
| |
| |
| |
| |
| | |
It is an unused holdover from long since removed functionality.
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
|