diff options
author | Shaohua Li <shli@fb.com> | 2017-08-14 15:05:00 -0700 |
---|---|---|
committer | Jens Axboe <axboe@kernel.dk> | 2017-08-23 08:54:12 -0600 |
commit | 2f54a613c9421ddd5897f861145ed0b8615a2ec4 (patch) | |
tree | f79d4b313cf52ff99236c30de19f5ba223abd60f /block | |
parent | deb78b419dfda333318a6ed1fe8e8c6245dd0d43 (diff) | |
download | linux-2f54a613c9421ddd5897f861145ed0b8615a2ec4.tar.gz linux-2f54a613c9421ddd5897f861145ed0b8615a2ec4.tar.bz2 linux-2f54a613c9421ddd5897f861145ed0b8615a2ec4.zip |
nullb: badbblocks support
Sometime disk could have tracks broken and data there is inaccessable,
but data in other parts can be accessed in normal way. MD RAID supports
such disks. But we don't have a good way to test it, because we can't
control which part of a physical disk is bad. For a virtual disk, this
can be easily controlled.
This patch adds a new 'badblock' attribute. Configure it in this way:
echo "+1-100" > xxx/badblock, this will make sector [1-100] as bad
blocks.
echo "-20-30" > xxx/badblock, this will make sector [20-30] good
If badblocks are accessed, the nullb disk will return IO error. Other
parts of the disk can accessed in normal way.
Signed-off-by: Shaohua Li <shli@fb.com>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'block')
0 files changed, 0 insertions, 0 deletions