]> code.ossystems Code Review - openembedded-core.git/commitdiff
populate-extfs.sh: error out if debugfs encounters some error
authorChen Qi <Qi.Chen@windriver.com>
Thu, 19 Jun 2014 02:11:33 +0000 (10:11 +0800)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Tue, 24 Jun 2014 09:57:32 +0000 (10:57 +0100)
Previously, even if we encounter some error when populating the
ext filesystem, we don't error out and the rootfs process still
succeeds.

However, what's really expected is that the populate-extfs.sh script
should error out if something wrong happens when using `debugfs' to
generate the ext filesystem. For example, if there's not enough block
in the filesystem, and allocating a block for some file fails, the
failure should not be ignored. Otherwise, we will have a successful
build but a corrupted filesystem.

The debugfs returns 0 as long as the command is valid. That is, even
if the command fails, the debugfs still returns 0. That's really a
pain here. That's why this patch checks the error output to see whether
there's any error logged.

Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
meta/recipes-devtools/e2fsprogs/e2fsprogs-1.42.8/populate-extfs.sh

index da3954ea7d417c4043a9171ac5c9a1bc42edc23c..23d97d39b6a559ac9fb38a16854084accdc9e5cc 100644 (file)
@@ -94,4 +94,9 @@ DEBUGFS="debugfs"
                echo "sif $SRC links_count $LN_CNT"
        done
        rm -fr $INODE_DIR
-} | $DEBUGFS -w -f - $DEVICE
+} | $DEBUGFS -w -f - $DEVICE 2>&1 1>/dev/null | grep '.*: .*'
+
+if [ $? = 0 ]; then
+    echo "Some error occured while executing [$DEBUGFS -w -f - $DEVICE]"
+    exit 1
+fi