Commit c46985e2 authored by Mike Snitzer's avatar Mike Snitzer

dm space map metadata: limit errors in sm_metadata_new_block

The "unable to allocate new metadata block" error can be a particularly
verbose error if there is a systemic issue with the metadata device.
Signed-off-by: default avatarMike Snitzer <snitzer@redhat.com>
Acked-by: default avatarJoe Thornber <ejt@redhat.com>
parent 42065460
...@@ -385,13 +385,13 @@ static int sm_metadata_new_block(struct dm_space_map *sm, dm_block_t *b) ...@@ -385,13 +385,13 @@ static int sm_metadata_new_block(struct dm_space_map *sm, dm_block_t *b)
int r = sm_metadata_new_block_(sm, b); int r = sm_metadata_new_block_(sm, b);
if (r) { if (r) {
DMERR("unable to allocate new metadata block"); DMERR_LIMIT("unable to allocate new metadata block");
return r; return r;
} }
r = sm_metadata_get_nr_free(sm, &count); r = sm_metadata_get_nr_free(sm, &count);
if (r) { if (r) {
DMERR("couldn't get free block count"); DMERR_LIMIT("couldn't get free block count");
return r; return r;
} }
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment