diff options
| author | Mike Snitzer <snitzer@redhat.com> | 2013-12-13 18:58:46 +0400 |
|---|---|---|
| committer | Mike Snitzer <snitzer@redhat.com> | 2014-01-07 19:11:46 +0400 |
| commit | c46985e211fa6d6895104cc4858e85e53e8c7731 (patch) | |
| tree | 34da7a05b5e15134a48aba4f85868226bc498539 /drivers/md | |
| parent | 42065460aed7201ec8adf0179a258a23bd1ebd78 (diff) | |
| download | linux-c46985e211fa6d6895104cc4858e85e53e8c7731.tar.xz | |
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>
Diffstat (limited to 'drivers/md')
| -rw-r--r-- | drivers/md/persistent-data/dm-space-map-metadata.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/drivers/md/persistent-data/dm-space-map-metadata.c b/drivers/md/persistent-data/dm-space-map-metadata.c index 58fc1eef7499..e93084419068 100644 --- 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; } |