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

On 20 March 2017 at 13:01, Daniel Schultz 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.

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

Am 20.03.2017 um 13:26 schrieb Burton, Ross: On 20 March 2017 at 12:18, Daniel Schultz > 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

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

On 20 March 2017 at 12:18, Daniel Schultz 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? Ross --

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

This patch avoids the creation of a corrupt EXT file system. Since there are no checks if a EXT file system was successfully created, this should add to prevent possible system failures. Signed-off-by: Daniel Schultz --- meta/classes/image_types.bbclass | 1 + 1 file