[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#597226: severity: Grave

On Fri, 2010-10-01 at 10:37 -0300, Gilberto Segundo wrote:
> 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?

This message means that data in memory will not be written to disk; we
do not consider that grave unless the failure is silent.  See

Please can you test without using the nvidia driver?


Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.

Attachment: signature.asc
Description: This is a digitally signed message part

Reply to: