On a long-running system with swapfc enabled swapfc_priority=50 can eventually reach 0 (generating kernel errors) as seen here: #135. Looping back to the value of swapfc_priority close to 0 is not a valid solution since that would mean that the highest priority swap file would be the first to be removed.
A better solution would be to disable swapfc_priority when it's 0 and let the kernel manage priorities (it has exclusive rights to priority -1...).
On a long-running system with swapfc enabled
swapfc_priority=50can eventually reach 0 (generating kernel errors) as seen here: #135. Looping back to the value ofswapfc_priorityclose to 0 is not a valid solution since that would mean that the highest priority swap file would be the first to be removed.A better solution would be to disable swapfc_priority when it's 0 and let the kernel manage priorities (it has exclusive rights to priority -1...).