1.3.3 i/o maxed out on Debian stretch/sid

[donald.m.motsinger]

Check the fragmentation of the database files with filefrag. I had a similar problem and seemed to have solved it by defragmenting them.

Disk fragmentation is inevitable... Do we need to prepare?

On an almost full 3.5TB node I had a problem with a lot of “ordersdb error: database is locked” errors and 99% I/O with 4 threads. The orders.db was heavily fragmented (~180000 extends). After defragmenting all databases the I/O is back to normal and so far no more errors.