summaryrefslogtreecommitdiff
path: root/sys/dev/raidframe
AgeCommit message (Collapse)Author
2000-07-14Fix the status reporting for copybacks. Thanks to Hubert Feyrer foroster
reporting the problem.
2000-06-29Nuke a printf that *I* added at least as early as Nov, 1998, and which isoster
as bogus now as it was then.
2000-06-11Nuke a (mostly) now-incorrect comment.oster
2000-06-04Remove outdated comment.oster
2000-06-04Merge rf_update_component_labels() and rf_final_update_component_labels().oster
2000-06-04Minor prototype cleanup.oster
2000-06-03Allow getting a component label from a spare disk.oster
2000-06-02Use 'componentN' rather than leaving blanks for non-existant disksoster
in the 'raidctl -s' output.
2000-06-01Make booted_device global (and booted_parition for consitency).matt
Eliminate it from header files and other extern definitions.
2000-05-31Oops.. reconstruction percentages were being reported incorrectly.oster
Thanks to Manuel Bouyer for noting this.
2000-05-30For a RAID 1 set that has N components, allow the set to auto-configure asoster
long as at least one of the master or the mirror is available for each of the N/2 'rows' of the set. (No, RAIDframe doesn't do N-way mirroring..) Thanks to Manuel Bouyer for noting the problem.
2000-05-30Use #include <sys/kernel.h> instead of a 'extern int hz'.oster
Make this file more readable.
2000-05-29Don't let the autodetection code get tripped up by negative mod-counters.oster
2000-05-29Fix a couple of typos. (Thanks Wiz! :) )oster
2000-05-28In the event that an up-to-date component cannot be located for a specificoster
position, see if there is a failed component still hanging around that we can use instead (but still mark it as failed). This leads to more reasonable behaviour (and fewer surprises!) when autoconfiguring and failed (or previously failed) components are still on the system.
2000-05-28We need to be slightly more clever during auto-configuration, to makeoster
sure that we a) don't ignore components with correct mod-counters, and b) do ignore components with bogus mod-counters.
2000-05-28Umm.. Complete is not equal to 'left to do'. Fix the math.oster
2000-05-28Abort any parity re-writes before unconfiguring a RAID set.oster
Partially addresses PR#10182.
2000-05-28When setting auto-config/rootable bits, only try to update theoster
component label if the component is actually alive.
2000-05-28- Add a mechanism for obtaining finer-grained 'progress' informationoster
regarding reconstructs, copybacks, etc. - RAID 0 doesn't do copybacks, but don't make raidctl sweat about it.
2000-05-27Components which match on everything but the mod_counter areoster
renegades, and must be handled correctly. In particular, they should be added to their old auto-config set, but then immediately released. Failing to do otherwise means that they potentialy end up in a different (and competing!) RAID set which may auto-configure in place of the correct one, and cause all sorts of chaos at auto-configure time.
2000-05-27Add a comment to clarify why we actually want the component label tooster
be considered a 'match' even if the mod_counter is wrong.
2000-05-27Checking parity re-write status makes no sense on RAID 0, but let'soster
return something reasonable anyway.
2000-05-23Const poison the layout name.thorpej
2000-05-19A foolish consistency; most parts of the kernel use bp->b_data, sothorpej
change these from bp->b_un.b_addr to bp->b_data, as well. This also allows us more flexibility to experiment with other data buffer types hung off of struct buf.
2000-05-19Add some missing casts of ioctl arg.minoura
Obviously autoconfiguration wouldn't work on big-endian machines.
2000-04-27Make sure the config structure allocated during autoconfiguration actuallyoster
gets initialized properly. Should fix PR#9816.
2000-04-17Revert last change (the last change was not necessarily desirable, andoster
had some other minor side-affects that were troublesome).
2000-04-16Don't allow configuration where the specified SectPerSU may result in IO largeroster
than MAXPHYS being sent to underlying devices. Addresses PR#9868. Will change if/when MAXPHYS goes bye-bye.
2000-03-31Minor cleanup of unneeded verbosity.oster
2000-03-31Print out the 'root' status of a RAID set during autoconfiguration.oster
2000-03-30Nuke 'register' from some function prototypes.oster
2000-03-30Remove register declarations.augustss
2000-03-27cleanup function prototypes.oster
2000-03-27Shuffle some prototypes to a more appropriate location.oster
2000-03-26Add bits for eventual support of deleteing components and movingoster
hot-spares into the main set.
2000-03-25Nuke a function prototype that shouldn't be here.oster
2000-03-22Fix up some autoconfigure messages. In particular, don't try printingoster
the value of an uninitialized variable. Noted by Luke Mewburn.
2000-03-20Just return "100% done" when asked about reconstruction progress onoster
a RAID0 set.
2000-03-13Fix doubled 'the's in comments.soren
2000-03-07Cleanup a couple of function declarations. No functional changes.oster
2000-03-07Create a new rf_close_component() to handle vnode operations for closingoster
components. Teach rf_UnconfigureVnodes() how to use it, and tell the copyback and reconstruction code about it too.
2000-03-07Move rf_UnconfigureVnodes to rf_netbsdkintf.c where it will be more at home.oster
Add prototype to rf_kintf.h, and nuke old prototypes from rf_disks.c and rf_driver.c .
2000-03-07rf_ protect the component label print routine, and make it more easilyoster
available to the rest of RAIDframe.
2000-03-07Nuke unused code.oster
2000-03-04Umm... don't allow attempts to configure the same RAID device multiple times.oster
The check was there, but the return() was missing :(
2000-03-04Reorganize some comments.oster
2000-03-04Garbage collect the (already disabled) "random" queue type.oster
2000-03-04Nuke an unneeded #define.oster
2000-03-03Use the common disk allocation code, rather doing things the old way.oster