| Age | Commit message (Collapse) | Author |
|
|
|
- fire up a new thread for parity re-writes, copybacks, and reconstructs.
The ioctl's which trigger these actions now return immediately.
- add progress accounting for the above actions.
- minor rototillage of rf_netbsdkintf.c to deal with all of the above.
|
|
|
|
than raid0. Fix that...
|
|
|
|
|
|
and cleanup arguments. While we're here, cleanup raidstrategy(), and nuke
a bunch of unused debugging stuff.
RAIDframe + softdeps now play very nicely together.
|
|
(this should have been committed with a previous fix for the same
problem in another function in this file :( )
|
|
|
|
|
|
disappeared a while back.
|
|
|
|
|
|
give any allocated memory back to the kernel so someone else can use it.
|
|
|
|
|
|
|
|
balancing in a RAID 1 set if we know that the parity might not
be up-to-date. Thanks to Thor for bringing this to my attention.
|
|
|
|
|
|
|
|
|
|
|
|
buy us anything at all.
|
|
allocation stuff.
|
|
|
|
performance measurement, but which would cause data corruption.
|
|
|
|
|
|
|
|
|
|
would panic in the case where the stripe width was 1 block.
|
|
The previous value may have been too high in some instances.
|
|
for quite some time.
|
|
passed in via ioctls.
|
|
is no longer needed at all.
|
|
|
|
|
|
provided by Peter Galbavy via OpenBSD.
|
|
|
|
slightly broken in the case where the RAID set did not support reconstruction.
|
|
|
|
provide more intuitive information about whether a component is clean
or not.
|
|
using a RAID 0, since RAID 0 can't handle those sorts of things.
|
|
and inform the user (as opposed to panicing the system!).
|
|
|
|
Also: spl protect rf_RewriteParity().
|
|
Also, check sooner for a RAID 0 set, since rewriting parity makes no
sense there either.
|
|
|
|
Without this, we have potentially bad interatctions with the pool
code.
|