Fixing priority of RAID check?

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

 



Hi!

When running a RAID check via:

$ echo check > /sys/block/md127/md/sync_action

The underlying system, especially a Linux container, becomes barely
usable. Webservers run into timeouts etc.

In top I see that md127_raid6 is run at priority 20. However some
(10+) other kworker processes do not and run at priority -20 and
consume a siginificant amount of sys CPU usage while the RAID check
is in progress.

Are there any suggested ways to tune/fix the priorization issue
I'm having?

The setup I'm having here is pretty low-cost, low-power. A Pi3
with 64 bit kernel, 5 SATA drives connected via USB, configured as
RAID6.

Regards, Linus
--
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