ID | H/W Model | RAM | Temp | BBU | FirmwareĬ0 | PERC H730P Adapter | 2048MB | 60C | Good | FW: 25. How do I know it's the same drive? Thanks to the use of megaclisas-status, the RAID HBA can be queried. Here's an identical drive (same model, same firmware) behind a RAID controller (a PERC H730P) on a different system (let's call that system System_B in the rest of this document): ~]# lsscsi Here's an SSD (a Samsung EVO 860 2Tb drive) attached to a SATA connector on a RHEL system (we will name that system System_A in the rest of this document): ~]# lsscsi
TRIM ENABLER 5 DRIVER
At the end of the SCSI I/O chain, the capabilities of a device boil down to the device itself, and the RAID driver your drive is attached to. If your SSDs are behind a RAID volume attached to a RAID controller (HPE's SmartArray, Dell's PERC, or anything based on LSI/Avago's MegaRAID), here's what happens: ~]# fstrim ~]# Here's an example using a Red Hat Enterprise Linux (RHEL) system: ~]# fstrim -av On most systems, getting the performance back is usually a simple matter of issuing a filesystem trim ( fstrim) command. Or maybe you once filled your SSD to 100%, and now you cannot get the original performance/IOPS back. Perhaps you have TLC (3bits per cell) or QLC (4bits per cell) drives instead of the usually more expensive enterprise-class SLC or MLC drives (the latter are less susceptible to a performance drop since they put aside more extra blocks to help with overwrites when the drive is at capacity). There are, however, some cases in which you may need to have the filesystem inform the drive of the blocks which it discarded.
Download RHEL 9 at no charge through the Red Hat Developer program.
0 kommentar(er)
