| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
use the standard bioq structures.
|
|
|
|
|
|
|
| |
When a drive is newly created, it's state is initially set to 'down',
so it won't allow saving the config to it (thus it will never know of
itself being created). Work around this by adding a new flag, that's
also checked when saving the config to a drive.
|
|
|
|
|
|
| |
*) Plug a possible memory leak. [1]
[1] obtained from: pjd@.
|
|
|
|
|
|
|
| |
the previous one failed and there are more than one plex in the volume.
This could have led to a flood of error messages on the console and
probably a deadlock in certain situations.
|
| |
|
| |
|
|
|
|
|
|
|
| |
This lowers the CPU usage of the worker thread and prevents a
possible live lock on non-SMP machines.
MFC candidate.
|
|
|
|
|
|
| |
currently not possible to do this while the volume is mounted.
MFC in: 1 week
|
|
|
|
|
|
|
|
|
|
| |
Analogous to the drive level, give each volume and plex a worker thread
that picks up and processes incoming and completed BIOs.
This should fix the data corruption issues that have come up a few
weeks ago and improve performance, especially of RAID5 plexes.
The volume level needs a little work, though.
|
|
|
|
|
| |
sends them down, and takes care of the finished bios. This makes it
easier to handle I/O errors at drive level.
|
|
|