[OE-core] [PATCH 3/3] meta: images: Add fsck to avoid corrupt EXT file systems

[Burton, Ross]

On 20 March 2017 at 13:01, Daniel Schultz <d.schultz at phytec.de> wrote:

> Doesn't mkfs returns an exit code if it wasn't successful?
>>
>> Yes, but it seems like mkfs can't handle everything.
>
> "The htree (hash tree) indexes directory entries by hash to speed up
> random directory accesses.  e2fsck can regenerate the indices, but the
> rest of e2fsprogs cannot create or maintain them."
> [http://www.spinics.net/lists/linux-ext4/msg55702.html]
>
> Currently, our boards have to reboot, because fsck exits with an error
> code of 1 at the first boot.
>

Fair enough, thanks.

Ross
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20170320/10309d6e/attachment-0002.html>