Single SATA WD 400GB: 1360.17 3 x 15K rpm sas RAID5 with write-through: 159.03 (YES, only 159!) same as above but with write-back enabled: 3133.45 Here is a real world example of the performance you can expect. You can use the command pveperf to have a general idea of performance. Some controllers support using an SSD so that a BBU isn't so important, but some SSDs do not deal with power loss well, do your research before relying on this solution.Ī RAID controller using write-through instead of write-back behaves very poorly. That ensures that any pending writes during a blackout can finish being saved as soon as power is restored. If you don't want to loose your data in case of black-out, you need a battery backup (BBU). This way the OS doesn't have to wait until data is physically written to disk, since they are immediately written to the cache and the controller will take care of finishing the subsequent write to the disk(s). Paramount feature for real raid controller if you want high performance is an on board cache and "write back" mode enabled. Embedded controllers are not supported in Proxmox, and if they do work, you are doing so at your own risk. For a RAID controller to be supported, it must be a "real" hardware controller rather than an embedded or "fake" RAID. Look for a line with RAID Controller or similar. You can use the lspci command in the Proxmox command line. This article lists some hardware raid controllers that are known to work well and some information configuring them. 11.1 Monitoring SMART status of disks in arrayĪ fast and reliable storage controller is one of the most important parts of a Proxmox VE server.
9 Smart Array (using in-kernel cciss driver).
0 kommentar(er)
