diff options
author | 2009-04-14 16:28:34 +1000 | |
---|---|---|
committer | 2009-04-14 16:28:34 +1000 | |
commit | acb180b0e335ad88acfed6c8a33e39c05b95dc49 (patch) | |
tree | fa980978bb66b178fd8c2f474194754139c0921d /kernel/mutex.c | |
parent | md: allow setting newly added device to 'in_sync' via sysfs. (diff) | |
download | linux-dev-acb180b0e335ad88acfed6c8a33e39c05b95dc49.tar.xz linux-dev-acb180b0e335ad88acfed6c8a33e39c05b95dc49.zip |
md: improve usefulness and accuracy of sysfs file md/sync_completed.
The sync_completed file reports how much of a resync (or recovery or
reshape) has been completed.
However due to the possibility of out-of-order completion of writes,
it is not certain to be accurate.
We have an internal value - mddev->curr_resync_completed - which is an
accurate value (though it might not always be quite so uptodate).
So:
- make curr_resync_completed be uptodate a little more often,
particularly when raid5 reshape updates status in the metadata
- report curr_resync_completed in the sysfs file
- allow poll/select to report all updates to md/sync_completed.
This makes sync_completed completed usable by any external metadata
handler that wants to record this status information in its metadata.
Signed-off-by: NeilBrown <neilb@suse.de>
Diffstat (limited to 'kernel/mutex.c')
0 files changed, 0 insertions, 0 deletions