diff options
author | 2011-07-28 11:31:47 +1000 | |
---|---|---|
committer | 2011-07-28 11:31:47 +1000 | |
commit | 2699b67223aca6b1450fc2f72e40fada952afc85 (patch) | |
tree | c84d0cbb763ad03cd770a218a37f0f1ec31118af /fs/jbd2/commit.c | |
parent | md: don't allow arrays to contain devices with bad blocks. (diff) | |
download | linux-rng-2699b67223aca6b1450fc2f72e40fada952afc85.tar.xz linux-rng-2699b67223aca6b1450fc2f72e40fada952afc85.zip |
md: load/store badblock list from v1.x metadata
Space must have been allocated when array was created.
A feature flag is set when the badblock list is non-empty, to
ensure old kernels don't load and trust the whole device.
We only update the on-disk badblocklist when it has changed.
If the badblocklist (or other metadata) is stored on a bad block, we
don't cope very well.
If metadata has no room for bad block, flag bad-blocks as disabled,
and do the same for 0.90 metadata.
Signed-off-by: NeilBrown <neilb@suse.de>
Diffstat (limited to 'fs/jbd2/commit.c')
0 files changed, 0 insertions, 0 deletions