Dell PowerVault MD3660f Administrator's Guide - Page 126

Troubleshooting, I/O may hang when a Device Mapper device is deleted before the volume is unmounted.

Page 126 highlights

• I/O may hang when a Device Mapper device is deleted before the volume is unmounted. • If the scsi_dh_rdac module is not included in initrd, slower device discovery may be seen and the syslog may become populated with buffer I/O error messages. • I/O may hang if the host server or storage array is rebooted while I/O is active. All I/O to the storage array should be stopped before shutting down or rebooting the host server or storage array. • With an MD Series Dense storage array, after a failed path is restored, failback does not occur automatically because the driver cannot auto-detect devices without a forced rescan. Run the command rescan_dm_devs to force a rescan of the host server. This restores the failed paths enabling failback to occur. • Failback can be slow when the host system is experiencing heavy I/O. The problem is exacerbated if the host server is also experiencing very high processor utilization. • The Device Mapper Multipath service can be slow when the host system is experiencing heavy I/O. The problem is exacerbated if the host server is also experiencing very high processor utilization. • If the root disk is not blacklisted in the multipath.conf file, a multipathing node may be created for the root disk. The command multipath -ll lists vendor/product ID, which can help identify this issue. • If upgrading from a previous version of SLES, uninstall and then reinstall the latest scsi_dh_rdac module on the updated SLES installation. Then update the kernel and install the MD Storage Manager from the DVD. Troubleshooting Question How can I check if multipathd is running? Answer Run the following command. /etc/init.d/multipathd status Why does the multipath -ll command output not show any devices? First verify if the devices are discovered or not. The command #cat / proc/scsi/scsi displays all the devices that are already discovered. Then verify the multipath.conf to ensure that it is been updated with proper settings. After this, run multipath. Then run multipath - ll, the new devices must show up. Why is a newly-mapped LUN not assigned Run rescan_dm_devs in any directory. This should bring up the a multipathing device node? devices. I removed a LUN. But the multipathing mapping is still available. The multipathing device is still available after you remove the LUNs. Run multipath -f to remove the multipathing mapping. For example, if a device related with /dev/dm-1 is deleted, you must run multipath -f /dev/dm-1 to remove /dev/dm-1 from DM mapping table. If multipathing daemon is stopped/restarted, run multipath -F to flush out all stale mappings. Failback does not happen as expected with the array. Sometimes the low level driver cannot auto-detect devices coming back with the array. Run rescan_dm_devs to rescan host server SCSI bus and re-aggregate devices at multipathing layer. 126

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175

I/O may hang when a Device Mapper device is deleted before the volume is unmounted.
If the
scsi_dh_rdac
module is not included in
initrd
, slower device discovery may be seen and the
syslog may become populated with buffer I/O error messages.
I/O may hang if the host server or storage array is rebooted while I/O is active. All I/O to the storage array should
be stopped before shutting down or rebooting the host server or storage array.
With an MD Series Dense storage array, after a failed path is restored, failback does not occur automatically
because the driver cannot auto-detect devices without a forced rescan. Run the command
rescan_dm_devs
to force a rescan of the host server. This restores the failed paths enabling failback to occur.
Failback can be slow when the host system is experiencing heavy I/O. The problem is exacerbated if the host
server is also experiencing very high processor utilization.
The Device Mapper Multipath service can be slow when the host system is experiencing heavy I/O. The problem
is exacerbated if the host server is also experiencing very high processor utilization.
If the root disk is not blacklisted in the
multipath.conf
file, a multipathing node may be created for the root disk.
The command
multipath –ll
lists vendor/product ID, which can help identify this issue.
If upgrading from a previous version of SLES, uninstall and then reinstall the latest
scsi_dh_rdac
module on
the updated SLES installation. Then update the kernel and install the MD Storage Manager from the DVD.
Troubleshooting
Question
Answer
How can I check if multipathd is running?
Run the following command.
/etc/init.d/multipathd status
Why does the multipath –ll command
output not show any devices?
First verify if the devices are discovered or not. The command
#cat /
proc/scsi/scsi
displays all the devices that are already discovered.
Then verify the
multipath.conf
to ensure that it is been updated with
proper settings. After this, run
multipath
. Then run
multipath –
ll
, the new devices must show up.
Why is a newly-mapped LUN not assigned
a multipathing device node?
Run
rescan_dm_devs
in any directory. This should bring up the
devices.
I removed a LUN. But the multipathing
mapping is still available.
The multipathing device is still available after you remove the LUNs. Run
multipath –f <device node for the deleted LUN>
to
remove the multipathing mapping. For example, if a device related
with
/dev/dm-1
is deleted, you must run
multipath –f /dev/dm-1
to remove
/dev/dm-1
from DM mapping table. If multipathing daemon is
stopped/restarted, run
multipath –F
to flush out all stale mappings.
Failback does not happen as expected
with the array.
Sometimes the low level driver cannot auto-detect devices coming back
with the array. Run
rescan_dm_devs
to rescan host server SCSI bus
and re-aggregate devices at multipathing layer.
126