STORAGE
The storage test evaluates the functionality of persistent online storage devices. You can run this test to verify that your system correctly identifies and operates various storage media. The test performs read and write operations on solid-state drives (SSDs) and memory cards.
- What the storage test covers
- There are many different kinds of persistent on-line storage devices available in systems today. The STORAGE test is designed to test anything that reports an ID_TYPE of "disk" in the udev database. This includes IDE, SCSI, SATA, SAS, and SSD drives, and PCIe SSD block storage devices. It also includes SD media, xD media, MemoryStick, and MMC cards. The test plan script reads through the udev database and looks for storage devices that meet these criteria. When it finds one, it records the device and its parent, and compares it to the parents of any other recorded devices. It does this to ensure that only devices with unique parents are tested. If the parent has not been seen before, the device is added to the test plan. This speeds up testing as only one device per controller is tested, as per the Policy Guide.
- RHEL version supported
-
- RHEL 8
- RHEL 9
- RHEL 10
- What the test does
-
The STORAGE test performs the following actions on all storage devices with a unique parent:
- The script looks through the partition table to locate a swap partition that is not on an LVM or software RAID device. If found, it deactivates it with swapoff and uses that space for the test. If no swap is present, the system can still test the drive if it is completely blank (no partitions). Note that the swap device must be active for this to work, since the test reads
/proc/swapsto find the swap partitions. The swap partition must not be inside any kind of software-based container, such as LVM or software RAID. Hardware RAID would work, since it would be invisible to the system. - The tool creates a filesystem on the device, either in a swap partition on the blank drive.
- The filesystem is mounted and the
fioordtcommand is used to test the device. Thefioordtcommand is an I/O test program and is a generic test tool capable of testing, reading, and writing to devices. Multiple sets of test patterns verify the functionality of storage devices. - After the mounted filesystem test, the filesystem is unmounted and a dt test is performed against the block device, ignoring the file system. The dt test uses the "direct" parameter to handle this.
- The script looks through the partition table to locate a swap partition that is not on an LVM or software RAID device. If found, it deactivates it with swapoff and uses that space for the test. If no swap is present, the system can still test the drive if it is completely blank (no partitions). Note that the swap device must be active for this to work, since the test reads
- Preparing for the test
-
You should install all the drives and storage controllers that are listed on the official test plan. In the case of multiple storage options, as many as can fit into the system can be tested in a single run. Alternatively, each storage device can be installed individually with its own test run. You can decide on the order of testing and number of controllers present for each test. Each logical drive attached to the system must contain a swap partition in addition to any other partitions, or be totally blank. This is to provide the test with a location to create a filesystem and run the tests. The use of swap partitions leads to a much quicker test, as devices left blank are tested in their entirety. They are almost always significantly larger than a swap partition placed on the drive.
Note If testing an SD media card, use the fastest card you can obtain. A Class 4 SD card may take 8 hours or more to run the test. A Class 10 or UHS 1/2 card can complete the test run in 30 minutes or less.
When it comes to choosing storage devices for the official test plan, the review team follows one rule. That rule is "one test per code path". This means we want to see a storage test run using every driver that a controller can use. The scenario of multiple drivers for the same controller usually involves RAID storage of some type. It’s common for storage controllers to use one driver when in regular disk mode and another when in RAID mode. Some even use multiple drivers depending on the RAID mode that they are in. The review team analyzes all storage hardware to determine the drivers needed. This ensures that all the testing requirements are fulfilled. That’s why you may see the same storage device listed more than once in the official test plan. Complete information on storage device testing is available in the Policy Guide.
- Running the test
-
The storage test is non-interactive. Run the following command and then select the appropriate
STORAGEtest name from the list that displays.rhcert-run - Run time, bare-metal
- The storage test takes approximately 22 minutes on a 6Gb/s SATA hard drive installed in a 2013-era workstation system. The same test takes approximately 3 minutes on a 6Gb/s SATA solid-state drive installed in a 2013-era workstation system. The required supportable test adds about a minute to the overall run time.