Bug#597226: severity: Grave
Today, I got the same error after the boot, more or less with three minutes in use.
The filesystem is remounted read-only and the messages like that are showed (Dmesg did not save the log because the filesystem become read only)
Aborting journal on device sda5-8.
EXT4-fs (sda5): Remounting filesystem read-only
EXT4-fs (sda5): delayed block allocation failed for inode 527890 at logical offset 0 with max blocks 1 with error -30
This should not happen!! Data will be lost
Once data will be lost, I think the severity should be changed to grave, shouldn't?
The system stopped and I had to restart the system using a live CD and fix the partition.
There is a similar bug in Ubuntu: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/528981