Ubuntu 22.04 Multipath I/O Problem with Dell VRTX
High-Level Architecture of Dell PowerEdge VRTX
In the previous article, I explain the issue I am running into when installing Ubuntu 22.04 on a Dell VRTX server. To understand a little bit more about what went wrong and potentially fix the problem, I tried to know how the Dell VRTX server was designed.
After some googling, I found the Technical Guide from Dell. It revealed a pretty interesting design of the system. The Dell VRTX system is designed to be a Cost-Effective Hyperconverged server system for a small office environment or remote office environment, where there are some compute power is needed but not on a large scale. One Dell VRTX chassis can host up to 4 server blades, up to 25 x 2.5 in. NLSAS, SAS, or SAS SSD hot-plug drives (not including the hard drive bays on the server blades), and 8 flexible PCIe slots. All those hard drives, PCIe slots, and network ports belong to the Dell VRTX chassis. The chassis management system can dynamically allocate resources to the server blades installed. Unlike traditional ways how the resources are shared via Ethernet connectivity in a data center environment, the Dell VRTX chassis share the resources via the PCIe switch. (Fabric B and Fabric C in the block diagram below.)
According to the block diagram, there are two of the Dell Shared PowerEdge RAID Controller (PERC) 8 connected to the PCIe switch fabrics. One to each of the fabrics. Each server blade has two PCIe connections, one to each of the PCIe switch fabrics too!
Dell Shared PowerEdge RAID Controller (PERC) 8 For Dell PowerEdge VRTX Systems
According to the User's Guide published by Dell,
The Dell Shared PowerEdge RAID Controller (PERC) 8 card installed on the Dell PowerEdge VRTX system supports Single Root Input Output Virtualization (SR-IOV). This feature allows multiple systems to share available hardware resources. The PERC 8 card allows four server modules to access a local shared storage. Each server module's operating system loads a Virtual Function (VF) driver that allows the server module to communicate with the Shared PERC 8 firmware. Virtual disks located on the shared storage can then be mapped to a server module.
In the Fault Tolerant Shared PERC 8 card configuration, the PowerEdge VRTX system has two Shared PERC 8 cards in an active-passive mode. In this configuration, each host server can access the same virtual disk through both cards. In the absence of a multipath driver, the operating system identifies the single disk as two identical disks. The multipath driver aggregates the two disks into a single disk with redundant access that is then presented to the operating system. The operating system’s multipath functionality determines the path chosen for any I/O sent to the virtual disk. Any I/O directed to the passive card is internally redirected to the active card for completion.
Now, it explains why our OS is seeing the same hard drive twice.
Multipath I/O
The multipath mentioned in Dell's document reminded me of the multipath we were using while I was managing the Oracle Database on Sun servers. Because the data stored in the database were so critical, there were a lot of performance and high-availability considerations built into the system. Database files were stored in some SAN storage systems connected via the SAN network. To address the single point of failure situation, there is more than one SAN switch in the network. Each sun server has two fiber connections to each of the SAN switches. The SAN storage system has similar connections. Each LUN defined in the SAN storage system are accessible via both fiber path. Both LUNs were mapped to the hard drives on the Sun server side. Then the multipath driver or software controls which hard drive to use when there is an I/O request for that drive. At any one time, only one of the paths was being used. If one path failed, it will use the 2nd path. So that there is no single point of failure for the storage system.
Linux OS does offer similar multipath functions. There must be something not done correctly.
Comments
Post a Comment