diff options
| author | Mike Snitzer <snitzer@redhat.com> | 2020-06-04 17:44:34 +0300 |
|---|---|---|
| committer | Mike Snitzer <snitzer@redhat.com> | 2020-06-05 21:59:58 +0300 |
| commit | 04867370ec40b708bd335df641182ddab0c59685 (patch) | |
| tree | df50c504f5644ac280c457c0aa7ceb7cb50ca807 /drivers/md/dm-mpath.c | |
| parent | 4c3f48380fedbd714fc95958f503c1b5adf3ee6b (diff) | |
| download | linux-04867370ec40b708bd335df641182ddab0c59685.tar.xz | |
dm mpath: add DM device name to Failing/Reinstating path log messages
When there are many DM multipath devices it really helps to have
additional context for which DM device a failed or reinstated path is
part of.
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
Diffstat (limited to 'drivers/md/dm-mpath.c')
| -rw-r--r-- | drivers/md/dm-mpath.c | 8 |
1 files changed, 6 insertions, 2 deletions
diff --git a/drivers/md/dm-mpath.c b/drivers/md/dm-mpath.c index b17da3046611..78cff42d987e 100644 --- a/drivers/md/dm-mpath.c +++ b/drivers/md/dm-mpath.c @@ -1285,7 +1285,9 @@ static int fail_path(struct pgpath *pgpath) if (!pgpath->is_active) goto out; - DMWARN("Failing path %s.", pgpath->path.dev->name); + DMWARN("%s: Failing path %s.", + dm_device_name(dm_table_get_md(m->ti->table)), + pgpath->path.dev->name); pgpath->pg->ps.type->fail_path(&pgpath->pg->ps, &pgpath->path); pgpath->is_active = false; @@ -1324,7 +1326,9 @@ static int reinstate_path(struct pgpath *pgpath) if (pgpath->is_active) goto out; - DMWARN("Reinstating path %s.", pgpath->path.dev->name); + DMWARN("%s: Reinstating path %s.", + dm_device_name(dm_table_get_md(m->ti->table)), + pgpath->path.dev->name); r = pgpath->pg->ps.type->reinstate_path(&pgpath->pg->ps, &pgpath->path); if (r) |