ext4: what are possible causes of "zero length extent" ?

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

 



Hello ext4 maintainers,

This is somewhat of a follow-on from the "ext4 filesystem bad extent error review"
thread from 2014.

Embedded system with main SoC Freescale i.MX6(ARM cortex A9), dual CPU, running
kernel 3.8.13.28, storage device is eMMC.
This still suffers from "zero length extent" ext4 file system corruptions.

I looked for upstream patches, but did not find any that explicitly fix "zero length extent"
problems apart from "2f97486 ext4: check for zero length extent explicitly".
That patch prevents the kernel panics but makes the affected file unreadable and
unremovable, which can be fixed by running fsck.

What are possible causes of "zero length extent", and are there upstream patches that
actually deal with some of those?

Regards,
Mark Craske
Mentor Graphics (UK) Ltd.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Reiser Filesystem Development]     [Ceph FS]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux FS]     [Yosemite National Park]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Device Mapper]     [Linux Media]

  Powered by Linux