Searched hist:da105ed5fd7edcc5e0df7dbacef4dadda74e7ebe (Results 1 – 2 of 2) sorted by relevance
| /openbmc/linux/drivers/md/ |
| H A D | dm-thin-metadata.h | diff da105ed5fd7edcc5e0df7dbacef4dadda74e7ebe Fri Jul 27 09:08:15 CDT 2012 Joe Thornber <ejt@redhat.com> dm thin metadata: introduce dm_pool_abort_metadata
Introduce dm_pool_abort_metadata to abort the current metadata
transaction. Generally this will only be called when bad things are
happening and dm-thin is trying to roll back to a good state for
read-only mode.
It's complicated by the fact that the metadata device may have failed
completely causing the abort to be unable to read the old transaction.
In this case the metadata object is placed in a 'fail' mode and
everything fails apart from destroying it.
Signed-off-by: Joe Thornber <ejt@redhat.com>
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
Signed-off-by: Alasdair G Kergon <agk@redhat.com>
|
| H A D | dm-thin-metadata.c | diff da105ed5fd7edcc5e0df7dbacef4dadda74e7ebe Fri Jul 27 09:08:15 CDT 2012 Joe Thornber <ejt@redhat.com> dm thin metadata: introduce dm_pool_abort_metadata
Introduce dm_pool_abort_metadata to abort the current metadata
transaction. Generally this will only be called when bad things are
happening and dm-thin is trying to roll back to a good state for
read-only mode.
It's complicated by the fact that the metadata device may have failed
completely causing the abort to be unable to read the old transaction.
In this case the metadata object is placed in a 'fail' mode and
everything fails apart from destroying it.
Signed-off-by: Joe Thornber <ejt@redhat.com>
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
Signed-off-by: Alasdair G Kergon <agk@redhat.com>
|