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

[Daniel Schultz]

Am 20.03.2017 um 13:26 schrieb Burton, Ross:
>
> On 20 March 2017 at 12:18, Daniel Schultz <d.schultz at phytec.de
> <mailto:d.schultz at phytec.de>> wrote:
>
>     Since there are no checks if a EXT file system was successfully created,
>     this should add to prevent possible system failures.
>
>
> 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.

> Ross

-- 
Mit freundlichen Grüßen,
With best regards,
   Daniel Schultz