On an busy lxc server 2.6.38-8-server amd64, I had elevator=cfq in the cmdline, no dpkg was running, yet it got stuck with the same symptoms (see the attached screenshot).
It is notable that the error happened across all dm- devices.
I ran the following command, let's see whether that would help:
for tt in /sys/fs/ext4/*/max_writeback_mb_bump; { echo 4 > $tt; }
On an busy lxc server 2.6.38-8-server amd64, I had elevator=cfq in the cmdline, no dpkg was running, yet it got stuck with the same symptoms (see the attached screenshot).
It is notable that the error happened across all dm- devices.
I ran the following command, let's see whether that would help: ext4/*/ max_writeback_ mb_bump; { echo 4 > $tt; }
for tt in /sys/fs/