Handling configuration changes, Informing the multipath daemon of resized devices, Tips for resizing devices with multipathing – Dell Acceleration Appliances for Databases User Manual
Page 71
In:
/lib/udev/rules.d/75-persistent-net-generator.rules
by adding this line:
DRIVERS=="mlx4_core", ENV{MATCHDEVID}="", ENV{MATCHIFTYPE}=""
When
udev
is updated, this line must be re-added.
HANDLING CONFIGURATION CHANGES
After volumes have been added, deleted, or resized, it is important to rescan LUNs on each affected
initiator system. The most convenient way to rescan LUNs is by running the
rescan-scsi-bus.sh
script. For example:
# rescan-scsi-bus.sh --forcerescan --hosts=34
Scanning SCSI subsystem for new devices
and remove devices that have disappeared
Scanning host 34 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs
Scanning for device 34 0 0 0 ...
OLD: Host: scsi34 Channel: 00 Id: 00 Lun: 00
Vendor: FUSIONIO Model: ION LUN Rev: 3243
Type: Direct-Access ANSI SCSI revision: 05
0 new device(s) found.
0 device(s) removed.
Failure to rescan LUNs after having reduced the size of a volume may lead to data loss.
Informing the Multipath Daemon of Resized Devices
After a multipath device is resized on Linux and a rescan is done, the multipath daemon needs to be
informed of the change. To do this, run the following commands:
# multipathd -k
multipathd> resize
multipathd> map
multipathd> exit
Tips for Resizing Devices with Multipathing
To resize a device, you should first resize it on the target/ION Accelerator side, and then on the
initiator side.
For RHEL 6.X and OEL 6.X, follow the steps out lined in the Red Hat Storage guide:
64