| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2000-11-20 | rationalize the use of b_flags for geteblk() buffers. | chs | |
| rather than assigning to the whole field, set or clear individual flags, which implies that the B_BUSY and B_INVAL flags will remain set. this allows us to make the assertion in brelse() that B_BUSY is set, which is the purpose of all this. | |||
| 2000-10-20 | Move disk_busy() and disk_unbusy() to more sane locations. Values | oster | |
| reported by 'systat iostat' and friends are now much more correct for RAIDframe devices. Thanks to Andrew Doran for poking me about this, and for suggestions on and review of the changes. | |||
| 2000-10-17 | Don't touch a failed component at all. Thanks to Robert Elz (kre) for | oster | |
| noting the problem and providing additional comments. | |||
| 2000-10-12 | Minor fixup for a printf(). Noted by Robert Elz. | oster | |
| 2000-09-21 | convert tsleep()->ltsleep(), which makes the kernel complain less | oster | |
| when compiled with LOCKDEBUG. | |||
| 2000-09-21 | Correct a few calls to VOP_CLOSE(). | oster | |
| 2000-09-11 | Be consistent: use mcpair->cond instead of mcpair->flag. | oster | |
| This also lets us clean up a bunch of cruft. | |||
| 2000-09-11 | Only reset the timer value if it actually accumlated time. | oster | |
| Otherwise it may never accumulate any time, and the recon delay will never happen. | |||
| 2000-09-08 | Make sure we are passing a locked vp to VOP_CLOSE. | oster | |
| 2000-08-20 | Use RF_WAIT_COND() to avoid locking errors. | thorpej | |
| 2000-08-20 | RF_COND_WAIT(): use ltsleep(). | thorpej | |
| RF_SIGNAL_COND(): use wakeup_one(). | |||
| 2000-08-19 | Remove a bogus VOP_UNLOCK. | oster | |
| 2000-08-19 | Don't try to initialize a component label on a failed component. | oster | |
| 2000-07-14 | Fix the status reporting for copybacks. Thanks to Hubert Feyrer for | oster | |
| reporting the problem. | |||
| 2000-06-29 | Nuke a printf that *I* added at least as early as Nov, 1998, and which is | oster | |
| as bogus now as it was then. | |||
| 2000-06-11 | Nuke a (mostly) now-incorrect comment. | oster | |
| 2000-06-04 | Remove outdated comment. | oster | |
| 2000-06-04 | Merge rf_update_component_labels() and rf_final_update_component_labels(). | oster | |
| 2000-06-04 | Minor prototype cleanup. | oster | |
| 2000-06-03 | Allow getting a component label from a spare disk. | oster | |
| 2000-06-02 | Use 'componentN' rather than leaving blanks for non-existant disks | oster | |
| in the 'raidctl -s' output. | |||
| 2000-06-01 | Make booted_device global (and booted_parition for consitency). | matt | |
| Eliminate it from header files and other extern definitions. | |||
| 2000-05-31 | Oops.. reconstruction percentages were being reported incorrectly. | oster | |
| Thanks to Manuel Bouyer for noting this. | |||
| 2000-05-30 | For a RAID 1 set that has N components, allow the set to auto-configure as | oster | |
| 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-30 | Use #include <sys/kernel.h> instead of a 'extern int hz'. | oster | |
| Make this file more readable. | |||
| 2000-05-29 | Don't let the autodetection code get tripped up by negative mod-counters. | oster | |
| 2000-05-29 | Fix a couple of typos. (Thanks Wiz! :) ) | oster | |
| 2000-05-28 | In the event that an up-to-date component cannot be located for a specific | oster | |
| 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-28 | We need to be slightly more clever during auto-configuration, to make | oster | |
| sure that we a) don't ignore components with correct mod-counters, and b) do ignore components with bogus mod-counters. | |||
| 2000-05-28 | Umm.. Complete is not equal to 'left to do'. Fix the math. | oster | |
| 2000-05-28 | Abort any parity re-writes before unconfiguring a RAID set. | oster | |
| Partially addresses PR#10182. | |||
| 2000-05-28 | When setting auto-config/rootable bits, only try to update the | oster | |
| component label if the component is actually alive. | |||
| 2000-05-28 | - Add a mechanism for obtaining finer-grained 'progress' information | oster | |
| regarding reconstructs, copybacks, etc. - RAID 0 doesn't do copybacks, but don't make raidctl sweat about it. | |||
| 2000-05-27 | Components which match on everything but the mod_counter are | oster | |
| 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-27 | Add a comment to clarify why we actually want the component label to | oster | |
| be considered a 'match' even if the mod_counter is wrong. | |||
| 2000-05-27 | Checking parity re-write status makes no sense on RAID 0, but let's | oster | |
| return something reasonable anyway. | |||
| 2000-05-23 | Const poison the layout name. | thorpej | |
| 2000-05-19 | A foolish consistency; most parts of the kernel use bp->b_data, so | thorpej | |
| 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-19 | Add some missing casts of ioctl arg. | minoura | |
| Obviously autoconfiguration wouldn't work on big-endian machines. | |||
| 2000-04-27 | Make sure the config structure allocated during autoconfiguration actually | oster | |
| gets initialized properly. Should fix PR#9816. | |||
| 2000-04-17 | Revert last change (the last change was not necessarily desirable, and | oster | |
| had some other minor side-affects that were troublesome). | |||
| 2000-04-16 | Don't allow configuration where the specified SectPerSU may result in IO larger | oster | |
| than MAXPHYS being sent to underlying devices. Addresses PR#9868. Will change if/when MAXPHYS goes bye-bye. | |||
| 2000-03-31 | Minor cleanup of unneeded verbosity. | oster | |
| 2000-03-31 | Print out the 'root' status of a RAID set during autoconfiguration. | oster | |
| 2000-03-30 | Nuke 'register' from some function prototypes. | oster | |
| 2000-03-30 | Remove register declarations. | augustss | |
| 2000-03-27 | cleanup function prototypes. | oster | |
| 2000-03-27 | Shuffle some prototypes to a more appropriate location. | oster | |
| 2000-03-26 | Add bits for eventual support of deleteing components and moving | oster | |
| hot-spares into the main set. | |||
| 2000-03-25 | Nuke a function prototype that shouldn't be here. | oster | |
