fedora 16, ext4 corruption

Ian Malone ibmalone at gmail.com
Mon Mar 4 13:21:03 UTC 2013

On 22 January 2013 11:08, Ian Malone <ibmalone at gmail.com> wrote:
> Hi,
> Is anyone else seeing problems with F16 ext4? I recently moved my
> install onto a new harddisc (which is reporting SMART is fine after
> running a full test) and did that by making a new ext4 fs (previously
> ext3) then rsyncing across. I'm now seeing occasional system 'freezes'
> (not hard freezes, but programs can fail to start or freeze. Yesterday
> the desktop completely stopped, but I was able to switch to a virtual
> console). dmesg reports errors to do with failing to write the journal
> and remounting read-only. On reboot an fsck is required, which finds
> some fixable problems. Obviously I'm wondering if it's the OS or the
> new disc. Was planning an F18 install soon which might help with one
> problem but not the other.
> Don't know if it's the 'ext4 data corruption bug' or if that's been
> fixed. http://www.phoronix.com/scan.php?page=news_item&px=MTIxNDQ

After a clean install of F18 I'm still having problems, though the
symptoms are different. dmesg shows "READ FPDMA QUEUED" and "skipping
hard reset" type errors. When this happens the entire desktop pauses
for a while then recovers. The exact behaviour seems to have changed
through the course of a number of kernel updates (most notably the
system seems to recover stably after it happens now). It's either a
hardware problem (though I've tried changing cables and the hard-disc
mounting, port was working with the previous drive) or a kernel one
(possibly buggy disc NCQ implementation needs workaround). Will file a
bug, but thought I should follow up here.


More information about the users mailing list