a0d72cb555
Trust only the data disk if the mirror is not known to be up-to-date.
...
(this should have been committed with a previous fix for the same
problem in another function in this file :( )
1999-12-09 02:26:09 +00:00
bd19af5aad
Nuke what's left of the DFSTRACE stuff.
1999-12-07 02:54:08 +00:00
e65f9b7c87
More cleanup. DKUSAGE (what little was left of it) goes bye-bye.
1999-12-07 02:40:27 +00:00
a38b721e5f
Nuke the last few bits of RF_DEBUG_ATOMIC that should have
...
disappeared a while back.
1999-12-07 02:13:28 +00:00
bed152a4e7
We don't support RF_DAG_TEST_ACCESS.
1999-12-03 03:35:30 +00:00
128e2e90c5
Nuke some duplicate code.
1999-12-03 03:18:45 +00:00
a038f90588
Kernel memory is not to be wasted. If we're bailing out because of an error,
...
give any allocated memory back to the kernel so someone else can use it.
1999-12-03 03:06:44 +00:00
3888a71ad1
Move LIST_INIT() to a more appropriate place.
1999-12-03 02:43:22 +00:00
5fd68b5d02
We must initialize bp->b_dep in InitBP().
1999-11-18 13:28:06 +00:00
e589155692
Remove some minor stuff that wasn't right, and wasn't even really used.
1999-11-17 01:16:37 +00:00
3949e74f78
If we have a choice: do not trust the parity disk for read
...
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.
1999-11-09 03:07:20 +00:00
fe5b29ca42
Nuke unused prototype.
1999-09-08 02:01:55 +00:00
83abb87d9a
Garbage collect more unused stuff.
1999-09-05 03:05:55 +00:00
9c01870db1
Remove more unused stuff.
1999-09-05 02:54:09 +00:00
cfbdda8843
Garbage collect some more stuff.
1999-09-05 02:24:58 +00:00
6158faa69d
Cleanup a bit more.
1999-09-05 01:58:11 +00:00
e57673d0d4
Remove one of the two bzero calls in RF_Calloc -- the 2nd one doesn't
...
buy us anything at all.
1999-09-05 01:46:35 +00:00
d8144e5848
More cleanup of unused stuff. This time we nuke a bunch of memory
...
allocation stuff.
1999-09-04 21:11:21 +00:00
cfd861fcd8
Minor cleanup of (now) unneeded RF_UTILITY checks.
1999-09-04 16:26:30 +00:00
b1615831d2
Nuke some unused code which, were it enabled, might be useful for
...
performance measurement, but which would cause data corruption.
1999-08-26 02:40:27 +00:00
770de7bb5a
Print a error message instead of panicing in rf_RecoveryPQFunc().
1999-08-15 03:44:46 +00:00
d516e7b571
Make these compile with RF_INCLUDE_RAID6.
1999-08-15 02:36:40 +00:00
ff6d7dd494
Cleanup a bit.
1999-08-15 02:36:03 +00:00
07cc4855f1
Minor cleanup. No functional changes.
1999-08-14 23:34:18 +00:00
4ba14d22b0
Fix an 'off-by-one' error in a RF_ASSERT which meant that a reconstruct
...
would panic in the case where the stripe width was 1 block.
1999-08-14 21:44:24 +00:00
740b9848cc
Decrease the number of outstanding IO's threashold slightly.
...
The previous value may have been too high in some instances.
1999-08-14 03:47:07 +00:00
6409e641a6
Remove a 'struct proc *'-passing abomination that's been bugging me
...
for quite some time.
1999-08-14 03:10:03 +00:00
4a058e82c5
Correct and/or improve detection of bogus row/column values
...
passed in via ioctls.
1999-08-14 02:41:36 +00:00
db2eaf18cf
rf_sys.h does not need to be #included in any of these files, and, actually,
...
is no longer needed at all.
1999-08-13 03:41:52 +00:00
1ec5208866
This file is no longer needed.
1999-08-13 03:31:20 +00:00
1aa6ce1041
Garbage collect rpcc().
1999-08-13 03:27:46 +00:00
02acd1910a
First kick at cleaning up the RF_ETIMER code. New timer handling code
...
provided by Peter Galbavy via OpenBSD.
1999-08-13 03:26:55 +00:00
eca431e87c
Nuke configuration of ETimer stuff during main configuration.
1999-08-13 03:25:01 +00:00
5cab826918
Clean up reconstruction accounting a bit. While it worked before, it was
...
slightly broken in the case where the RAID set did not support reconstruction.
1999-08-13 01:43:33 +00:00
33e458640f
Garbage collect unused struct rf_test_acc.
1999-08-11 02:20:35 +00:00
31b98d3572
When reporting the status of a component during configuration,
...
provide more intuitive information about whether a component is clean
or not.
1999-08-10 22:56:20 +00:00
620eda50c7
Don't allow reconstructs, copybacks, or forced failures of components if
...
using a RAID 0, since RAID 0 can't handle those sorts of things.
1999-08-10 22:46:59 +00:00
0b08c839eb
Don't go ape if there is a problem verifying the parity. Note the condition
...
and inform the user (as opposed to panicing the system!).
1999-08-10 22:19:27 +00:00
49efd10006
Oops. Make minor change that I forgot when adding the parity check ioctl.
1999-08-10 21:41:37 +00:00
a3aefdaee3
Add support for easily checking the parity status from userland.
...
Also: spl protect rf_RewriteParity().
1999-08-10 18:18:30 +00:00
a531d8c31e
Trying to rebuild parity on a degraded set is bogus, so don't allow that.
...
Also, check sooner for a RAID 0 set, since rewriting parity makes no
sense there either.
1999-08-10 01:53:26 +00:00
e0c8203cb3
Nuke unused #define.
1999-08-03 22:07:39 +00:00
5cef006d40
Need to splbio()/splx() protect some of the reconstruction stuff.
...
Without this, we have potentially bad interatctions with the pool
code.
1999-07-21 03:15:26 +00:00
ce7cb7114d
rf_UnconfigureVnodes() needs to be called in the DO_RAID_FAIL macro.
1999-07-19 01:36:07 +00:00
0c7600ca4e
sectorsPerStripeUnit should be larger than 0. If it isn't, simply fail.
...
(Thanks to Thor Lancelot Simon for noting the problem).
1999-07-19 01:35:19 +00:00
324c76b3d9
Once upon a time, long long ago, there was a "fix" added to the
...
RAIDframe driver to stop it from eating too much kernel memory when
writing data. But that fix had a nasty side-affect of hurting write
performance (*much* more than I thought it would). These changes nuke
that "fix", and instead put in a more reasonable mechanism for limiting
the number of simultaneous IO's which can be happening for each RAID device.
The result is a noticeable improvement in write throughput. The End.
1999-07-08 00:45:23 +00:00
5f1ede624f
Make the kthread API a bit friendlier to loadable kernel modules.
1999-07-06 21:51:22 +00:00
86abd11d42
Remember to pass down the proc pointer when adding a hot spare.
...
(Thanks to Martin J. Laubach for helping track this one down.)
1999-06-13 20:36:17 +00:00
8c39e1bf02
When adding a hot spare, remember to lock down the main raidPtr
...
structure before mucking with its contents.
1999-06-04 02:02:39 +00:00
60769ea563
At config time, initialize a small amount of space for the disk queues
...
corresponding to the hot spares. We'll need that space when a spare is
actually added. Huge Thanks to Martin Laubach for helping track this down.
1999-06-04 01:51:00 +00:00
3af0ce9e19
Don't count two problems with a single component as two
...
component failures! Also: remember to configure the disk queues for
the spares -- failure to do that is Bad(tm).
Huge Thanks to Martin Laubach for helping track this down.
1999-06-04 01:50:01 +00:00
daf0e5b05c
Replace two instances of TNF copyright with one (was replicated for two
...
separate contributers).
1999-05-13 21:46:17 +00:00
4882ae464f
Fix a couple of compiler warnings on the Alpha. Pointed out by Tim Rightnour.
1999-04-12 19:39:59 +00:00
9f560505d4
Allow re-writing parity on a RAID 0 to trivially succeed, and to set the
...
clean bit. This is somewhat bogus as RAID 0 does not have any parity,
but is a slightly cleaner than other solutions, and makes the handling
of clean bits for RAID 0 consistent with the handling of clean bits at
other RAID levels.
1999-04-07 14:17:10 +00:00
14de6c2418
Cleanup shutdown code - garbage collect (now) unused shutdownhooks() stuff.
1999-03-27 01:26:37 +00:00
efe288e520
Correct a component label problem where a RAID 1 set with a
...
failed component would not configure properly in certain situations.
1999-03-18 03:02:38 +00:00
2ec2c2045f
Cleanup rf_RewriteParity() and rf_VerifyParity(). Nuke unused stuff,
...
and make more readable.
1999-03-14 22:10:46 +00:00
414b788837
Disallow interrupting parity re-writes or copybacks by removing PCATCH
...
from the tsleep()'s (they probably shouldn't have been there in the
first place!). Making parity re-writing and copybacks interruptable
will require re-designing how a few things are done (e.g. how memory
is freed for structures shipped off to routines that run asynchronously
relative to the calling routine). Fix a few other tsleep's while we're at it.
1999-03-14 21:53:31 +00:00
cd0a696176
Cleanup raidattach: move rf_boot's functionality to raidattach, and
...
nuke rf_boot(). Cleanup raidopen().
1999-03-09 03:53:18 +00:00
e39fe5e2fe
Cleanup unused cruft.
1999-03-09 03:52:41 +00:00
29daf0c77d
rf_update_component_labels() now lives here. Re-work clean-bit
...
support a little: clean-bits now also get frobbed on partition
opening/closing, rather than just at device configuration and device
unconfiguration. Schedule shutdownhooks() stuff for nukage at a later
date, since it isn't really necessary any more.
1999-03-09 02:59:25 +00:00
585c77594e
Move rf_update_component_labels() from here to rf_netbsdkintf.c.
1999-03-09 02:57:29 +00:00
98d8c12355
Update for recent changes including component label support, clean
...
bits, rebuilding components in-place, adding hot spares, shutdownhooks, etc.
1999-03-02 03:18:48 +00:00
ee9187f136
After a vn_close(), set the vnode * to NULL so we don't try closing it
...
again later.
1999-02-27 03:43:20 +00:00
a76f56098c
Do the VOP_UNLOCK() on an initialized vp, rather than random garbage.
1999-02-27 01:48:13 +00:00
65be57243f
Minor cleanups and code rearranging. Now knows a little about component
...
labels and how to deal with hot-adding spare components. Still work in
progress -- component labels and hot-adding are not enabled (yet).
1999-02-24 00:00:03 +00:00
be9eca67c8
Cleanup/remove unused cruft. First kick at component labels and clean bits.
...
Still work in progress. New code is there, but not enabled yet.
1999-02-23 23:57:53 +00:00
07b6b89dce
Move vnode cleanup code into one place. Cleanup a bit.
1999-02-23 23:55:29 +00:00
0d29172def
Do a VOP_UNLOCK() before a vn_close().
1999-02-23 23:53:37 +00:00
6d72c8f0e7
Minor cleanups that got missed last time through.
1999-02-11 01:23:32 +00:00
0014588545
Phase 2 of the RAIDframe cleanup. The source is now closer to KNF
...
and is much easier to read. No functionality changes.
1999-02-05 00:06:06 +00:00
58f7de552d
Nuke more bits of RAIDframe "demo" code. We're not "demoing" here,
...
we're doing the Real Thing!
1999-01-26 04:40:03 +00:00
472e649cd8
More simulator bits going bye-bye.
1999-01-26 04:05:01 +00:00
c52883118d
This stuff is no longer needed. Mostly simulator bits.
1999-01-26 03:56:21 +00:00
a37be85529
rf_ccmn.h no longer needed. Nuke it's inclusion from rf_disks.c.
1999-01-26 03:49:49 +00:00
d94a2c5b2a
These files are not used in the kernel driver. We don't need them any more.
1999-01-26 03:07:10 +00:00
1eecf8e491
RAIDframe cleanup, phase 1. Nuke simulator support, user-land driver,
...
out-dated comments, and other unneeded stuff. This helps prepare
for cleaning up the rest of the code, and adding new functionality.
No functional changes to the kernel code in this commit.
1999-01-26 02:33:49 +00:00
edd259d12e
Make it so raidframe will only perform synchronous writes, and async
...
reads. This avoids a problem where many writes will cause the driver
to allocate way too much memory.
This needs to change to a queueing system later, which will provide a
way to limit the memory consumed by the driver.
Without these changes, raidframe would use 24M or more on my machine when
the buffer cache dumped all its dirty blocks. Now it uses around 200k
or so.
1999-01-15 17:55:52 +00:00
d8f3aefec7
Use M_RAIDFRAME.
1999-01-14 22:49:05 +00:00
4128f9df1e
Duh... check that malloc() hasn't returned a NULL *before* we zero the buffer,
...
not after. Pointed out by Michael Graff.
1999-01-14 20:29:38 +00:00
e392d933c8
Clean up some debugging stuff, and make it compile without warnings
...
with -DDEBUG on alphas.
1998-12-22 20:03:14 +00:00
1b04131eff
Try a bit harder to detect the physical failure of a component, and to
...
mark that component as dead. Physical failures are handled much better now.
1998-12-03 15:14:40 +00:00
3f3d8e85e6
If a configuration fails due to a non-existant spare, remember to release
...
any previously allocated components before bailing. Credit to Manuel Bouyer
for noticing this.
1998-12-03 15:06:25 +00:00
679de7e878
Fix (potential) referencing of null pointer in (verbose) debugging mode.
1998-12-03 14:58:24 +00:00
b66ca92f4a
Initialize (to NULL) a variable in rf_CvscanPromote().
1998-11-18 15:13:51 +00:00
7eac22153a
Use types.h, endian.h and limits.h to configure the RAIDframe
...
types correctly for all hardware platforms.
1998-11-16 04:14:10 +00:00
3f1c86b59e
compile with DEBUG=1
1998-11-15 00:01:24 +00:00
a0c0e7eff1
fix egcs warning
1998-11-13 13:47:56 +00:00
acdd660ace
fix callback type
1998-11-13 13:45:15 +00:00
a9c167b273
prototype un-prototyped functions
1998-11-13 11:51:55 +00:00
8e893eff9e
Add braces around 'if' to pacify egcs
1998-11-13 11:48:26 +00:00
38a3987b69
RAIDframe, version 1.1, from the Parallel Data Laboratory at
...
Carnegie Mellon University. Full RAID implementation, including
levels 0, 1, 4, 5, 6, parity logging, and a few other goodies.
Ported to NetBSD by Greg Oster.
1998-11-13 04:20:26 +00:00
oster