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: Mike Snitzer <snitzer@redhat.com>
Acked-by: Joe Thornber <ejt@redhat.com>

diff --git a/drivers/md/persistent-data/dm-space-map-metadata.c b/drivers/md/persistent-data/dm-space-map-metadata.c
index 58fc1eef7499e1923ef00095502c1e1b49f50ffb..e93084419068b6039c69204074876a5e81f2587d 100644 (file)
--- a/drivers/md/persistent-data/dm-space-map-metadata.c
+++ b/drivers/md/persistent-data/dm-space-map-metadata.c
@@ -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);
        if (r) {
-               DMERR("unable to allocate new metadata block");
+               DMERR_LIMIT("unable to allocate new metadata block");
                return r;
        }
 
        r = sm_metadata_get_nr_free(sm, &count);
        if (r) {
-               DMERR("couldn't get free block count");
+               DMERR_LIMIT("couldn't get free block count");
                return r;
        }