MD raid and different elevators (disk i/o schedulers)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




I have tried to find information about this question in google, but found nothing.

The question is: are there issues using different disk i/o schedulers (by appending elevator=xxx to the kernel boot command line) when using md RAID1 or RAID5?

I seem to remember that someone told me that using elevator=deadline can cause perfectly good disks to be kicked from the RAID because of some latency issues that make the disk seem unresponsive (and dead) to the raid software.

Is this true? Are there compatibility issues using different i/o schedulers with software raid?


Thanks

--

Fabio "Kurgan" Muzzi

(worried Linux sysadmin)

--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux