| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Reported by: andre
|
|
|
|
|
|
|
| |
write failure probability.
- Allow to specify an error number to return of failure.
MFC after: 3 days
|
| |
|
| |
|
|
|
|
|
| |
Found by: Coverity Prevent(tm)
MFC after: 3 days
|
|
|
|
| |
Reported by: Eric Anderson <anderson@centtech.com>
|
|
|
|
| |
Reported by: glebius
|
|
|
|
|
|
|
|
| |
- number of read I/O requests,
- number of write I/O requests,
- number of read bytes,
- number of written bytes.
Add 'reset' subcommand for resetting statistics.
|
| |
|
|
|
|
| |
ignored.
|
| |
|
|
|
|
|
|
|
|
| |
set gp->softc to NULL and return ENXIO when it is NULL, so GEOM
will not panic or hang, but unload one device on every 'unload'.
This make 'unload' command usable, but it have to be executed
<number of devices> + 1 times.
- Made use of 'pp' variable.
|
|
|
|
|
|
|
|
|
|
| |
provider.
- Bump version number.
This allows for a quite interesting trick. One can setup a stripe with
stripe size of 512 bytes and create transparent provider on top of it
with sector size equal to <ndisks> * 512. The result will be something
like RAID3 without parity disk (every access will touch all disks).
|
|
|
|
| |
consumers. Teach STRIPE, CONCAT and NOP classes about this improvement.
|
|
|
|
|
| |
-o offset - specifies where to start on the original provider
-s size - specifies size of the transparent provider
|
| |
|
| |
|
|
|
|
| |
- Bump version number.
|
|
it is very useful for tests. One is able to destroy its provider
forcibly if wants to test how other class handle such events.
One is also able to specify failure probability to check how other
classes handle I/O errors.
Supported by: Wheel - Open Technologies - http://www.wheel.pl
|