Veritas InfoScale™ 7.4.3 Release Notes - Linux
- Introduction and product requirements
- Changes introduced in InfoScale 7.4.3
- Limitations
- Virtualization software limitations
- Storage Foundation software limitations
- Dynamic Multi-Pathing software limitations
- Veritas Volume Manager software limitations
- Veritas File System software limitations
- SmartIO software limitations
- Replication software limitations
- Cluster Server software limitations
- Limitations related to bundled agents
- Limitations related to VCS engine
- Veritas cluster configuration wizard limitations
- Limitations related to the VCS database agents
- Cluster Manager (Java console) limitations
- Limitations related to LLT
- Limitations related to I/O fencing
- Limitations related to bundled agents
- Storage Foundation Cluster File System High Availability software limitations
- Storage Foundation for Oracle RAC software limitations
- Storage Foundation for Databases (SFDB) tools software limitations
- Known issues
- Issues related to installation and upgrade
- Storage Foundation known issues
- Dynamic Multi-Pathing known issues
- Veritas Volume Manager known issues
- Veritas File System known issues
- Virtualization known issues
- Replication known issues
- Cluster Server known issues
- Operational issues for VCS
- Issues related to the VCS engine
- Issues related to the bundled agents
- Issues related to the VCS database agents
- Issues related to the agent framework
- Cluster Server agents for Volume Replicator known issues
- Issues related to Intelligent Monitoring Framework (IMF)
- Issues related to global clusters
- Issues related to the Cluster Manager (Java Console)
- VCS Cluster Configuration wizard issues
- LLT known issues
- I/O fencing known issues
- Operational issues for VCS
- Storage Foundation and High Availability known issues
- Storage Foundation Cluster File System High Availability known issues
- Storage Foundation for Oracle RAC known issues
- Oracle RAC known issues
- Storage Foundation Oracle RAC issues
- Storage Foundation for Databases (SFDB) tools known issues
- Application isolation feature known Issues
- Cloud deployment known issues
- Issues related to Veritas InfoScale Storage in Amazon Web Services cloud environments
- Container deployment know issues
Paths cannot be enabled inside a KVM guest if the devices have been previously removed and re-attached from the host
LUNs are exported to the KVM guest via virtio-scsi interface. When some physical link between the host and the SAN array fails for a certain time (45-60 seconds by default), the HBA driver in the host will remove the timed-out devices. When the link is restored, these devices will be re-attached to the host; however, the access from inside the KVM guest to these devices cannot be automatically restored too without rebooting the system or manually re-attaching the devices. For DMP, these subpaths will remain in DISABLED state.
This is a known limitation of KVM.
Workaround:
From the KVM host, tune the dev_loss_tmo parameter of the Fibre Channel ports to a very large value, and set the fast_io_fail_tmo parameter to 15.
To restore access to the timed-out devices
- Add the following lines into
/dev/udev/rules.d/40-kvm-device
file:KERNEL=="rport-*", SUBSYSTEM=="fc_remote_ports", ACTION=="add", \ RUN+="/bin/sh -c 'grep -q off \ /sys/class/fc_remote_ports/%k/fast_io_fail_tmo;if [ $? -eq 0 ]; \ then echo 15 > /sys/class/fc_remote_ports/%k/fast_io_fail_tmo 2> \ /dev/null;fi;'" KERNEL=="rport-*", SUBSYSTEM=="fc_remote_ports", ACTION=="add", \ RUN+="/bin/sh -c 'echo 8000000 > \ /sys/class/fc_remote_ports/%k/dev_loss_tmo 2> /dev/null'"
- Create the
/etc/modprobe.d/qla2xxx.conf
file with the following content:options qla2xxx qlport_down_retry=8000000
- Create the
/etc/modprobe.d/scsi_transport_fc.conf
with the following content:options scsi_transport_fc dev_loss_tmo=8000000
- Rebuild the
initrd
file and reboot.