3 ms·

Thanks a lot for elaborating. I'm traveling at the moment, but I'm going to try reproducing this issue once I'm back in town. IIRC I did do partitioning myself,

• ryao 2y ago
  > Upd mq-deadline for all drives seems to be `none` for me. I am not sure what you mean by that. One possibility is that the ones who reported mq-deadline did better were on either kyber or bfq, rather than none. The none elevator should be best for ZFS.
  • ein0p 2y ago
    I mean that it's already "none" on the machine where I encountered this bug. "Upd" was merely to signal that I've made an edit to my post.
    • ryao 2y ago
      The mq-deadline part is what confused me. That is a competing option for the Linux IO elevator that runs under ZFS. Anyway, I understand now and thanks for the data point. I added a list of questions to GitHub that could help narrow things down if you take time to answer them. I will be watching the GitHub thread regularly, so I will see it if you post the answers after you return from your travels.
      • ein0p 2y ago
        I was confused, actually, not you. The output was: cat /sys/dev/block/8:176/queue/scheduler [mq-deadline] none However, this output does not mean what I thought it did - it means that mq-deadline is in use. If I do echo "none" | sudo tee /sys/dev/block/8:176/queue/scheduler This changes to cat /sys/dev/block/8:176/queue/scheduler [none] mq-deadline