Ewan D. Milne
2014-02-28 15:31:55 UTC
Testing has revealed an issue with multipath complaining about
the capacity changing on one path to a device, and discontinuing
the use of that path. This is undesirable, as it appears that
at least one storage array does not always report the UA for
CAPACITY DATA HAS CHANGED when a LUN is resized. Comment out
all the rules that rescan a device when attributes change until
this can be investigated more thoroughly.
Note that this is a preexisting issue, since anyone could have
rescanned a device via sysfs. But the udev rules made this
automatic, so it could now occur all the time.
Leave the rule for REPORTED LUNS DATA HAS CHANGED in place, though.
Signed-off-by: Ewan D. Milne <***@redhat.com>
---
tools/udev/90-scsi-ua.rules | 8 ++++----
1 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/tools/udev/90-scsi-ua.rules b/tools/udev/90-scsi-ua.rules
index 694e29f..193e22c 100644
--- a/tools/udev/90-scsi-ua.rules
+++ b/tools/udev/90-scsi-ua.rules
@@ -1,5 +1,5 @@
-ACTION=="change", SUBSYSTEM=="scsi", ENV{SDEV_UA}=="INQUIRY_DATA_HAS_CHANGED", TEST=="rescan", ATTR{rescan}="x"
-ACTION=="change", SUBSYSTEM=="scsi", ENV{SDEV_UA}=="CAPACITY_DATA_HAS_CHANGED", TEST=="rescan", ATTR{rescan}="x"
-ACTION=="change", SUBSYSTEM=="scsi", ENV{SDEV_UA}=="THIN_PROVISIONING_SOFT_THRESHOLD_REACHED", TEST=="rescan", ATTR{rescan}="x"
-ACTION=="change", SUBSYSTEM=="scsi", ENV{SDEV_UA}=="MODE_PARAMETERS_CHANGED", TEST=="rescan", ATTR{rescan}="x"
+#ACTION=="change", SUBSYSTEM=="scsi", ENV{SDEV_UA}=="INQUIRY_DATA_HAS_CHANGED", TEST=="rescan", ATTR{rescan}="x"
+#ACTION=="change", SUBSYSTEM=="scsi", ENV{SDEV_UA}=="CAPACITY_DATA_HAS_CHANGED", TEST=="rescan", ATTR{rescan}="x"
+#ACTION=="change", SUBSYSTEM=="scsi", ENV{SDEV_UA}=="THIN_PROVISIONING_SOFT_THRESHOLD_REACHED", TEST=="rescan", ATTR{rescan}="x"
+#ACTION=="change", SUBSYSTEM=="scsi", ENV{SDEV_UA}=="MODE_PARAMETERS_CHANGED", TEST=="rescan", ATTR{rescan}="x"
ACTION=="change", SUBSYSTEM=="scsi", ENV{SDEV_UA}=="REPORTED_LUNS_DATA_HAS_CHANGED", RUN+="scan-scsi-target $env{DEVPATH}"
the capacity changing on one path to a device, and discontinuing
the use of that path. This is undesirable, as it appears that
at least one storage array does not always report the UA for
CAPACITY DATA HAS CHANGED when a LUN is resized. Comment out
all the rules that rescan a device when attributes change until
this can be investigated more thoroughly.
Note that this is a preexisting issue, since anyone could have
rescanned a device via sysfs. But the udev rules made this
automatic, so it could now occur all the time.
Leave the rule for REPORTED LUNS DATA HAS CHANGED in place, though.
Signed-off-by: Ewan D. Milne <***@redhat.com>
---
tools/udev/90-scsi-ua.rules | 8 ++++----
1 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/tools/udev/90-scsi-ua.rules b/tools/udev/90-scsi-ua.rules
index 694e29f..193e22c 100644
--- a/tools/udev/90-scsi-ua.rules
+++ b/tools/udev/90-scsi-ua.rules
@@ -1,5 +1,5 @@
-ACTION=="change", SUBSYSTEM=="scsi", ENV{SDEV_UA}=="INQUIRY_DATA_HAS_CHANGED", TEST=="rescan", ATTR{rescan}="x"
-ACTION=="change", SUBSYSTEM=="scsi", ENV{SDEV_UA}=="CAPACITY_DATA_HAS_CHANGED", TEST=="rescan", ATTR{rescan}="x"
-ACTION=="change", SUBSYSTEM=="scsi", ENV{SDEV_UA}=="THIN_PROVISIONING_SOFT_THRESHOLD_REACHED", TEST=="rescan", ATTR{rescan}="x"
-ACTION=="change", SUBSYSTEM=="scsi", ENV{SDEV_UA}=="MODE_PARAMETERS_CHANGED", TEST=="rescan", ATTR{rescan}="x"
+#ACTION=="change", SUBSYSTEM=="scsi", ENV{SDEV_UA}=="INQUIRY_DATA_HAS_CHANGED", TEST=="rescan", ATTR{rescan}="x"
+#ACTION=="change", SUBSYSTEM=="scsi", ENV{SDEV_UA}=="CAPACITY_DATA_HAS_CHANGED", TEST=="rescan", ATTR{rescan}="x"
+#ACTION=="change", SUBSYSTEM=="scsi", ENV{SDEV_UA}=="THIN_PROVISIONING_SOFT_THRESHOLD_REACHED", TEST=="rescan", ATTR{rescan}="x"
+#ACTION=="change", SUBSYSTEM=="scsi", ENV{SDEV_UA}=="MODE_PARAMETERS_CHANGED", TEST=="rescan", ATTR{rescan}="x"
ACTION=="change", SUBSYSTEM=="scsi", ENV{SDEV_UA}=="REPORTED_LUNS_DATA_HAS_CHANGED", RUN+="scan-scsi-target $env{DEVPATH}"
--
1.7.1
1.7.1