summaryrefslogtreecommitdiff
path: root/recipes-bsp
diff options
context:
space:
mode:
authorStefan Christ <s.christ@phytec.de>2016-02-25 15:08:00 +0100
committerStefan Müller-Klieser <s.mueller-klieser@phytec.de>2016-02-26 09:34:56 +0100
commitb0090e304c913d1e2c24b608d0b9d6fc6d7830a1 (patch)
tree4ae08323cdbb23f2cd8f28f6bd3ac3557203fe2a /recipes-bsp
parent9c0506167dc5dd2de8e85f7add52b67bab1f41d8 (diff)
downloadmeta-phytec-b0090e304c913d1e2c24b608d0b9d6fc6d7830a1.tar.bz2
meta-phytec-b0090e304c913d1e2c24b608d0b9d6fc6d7830a1.zip
barebox: env: force filesystem repair by fsck
Using the kernel parameter fsck.repair=yes enables the strongest fixing mode of fsck. Documentation of fsck.repair: "yes" will answer yes to all questions by fsck (https://www.freedesktop.org/software/systemd/man/systemd-fsck@.service.html) In fact the kernel parameter advices the systemd-fsck program to pass the parameter '-y' to fsck.ext4. This fixes filesystem errors more aggressively than the default '-p' (Automatically repair ("preen") the file system). This option should make the system more powercut and failure resistant. Since for embedded devices there is no system administrator who can handle a broken filesystem, the system should just try as hard as it can to boot and start the main application. The main application can fail, because of the broken filesystem, too, but it's better to start it than giving up before. So it has a chance to detect errors and show an appropriate message to the end user. The question, what to do if the ext4 filesystem is corrupted, is open for debate and maybe depends on the end user application, e.g. consumer, automotive or safety critical applications. Signed-off-by: Stefan Christ <s.christ@phytec.de> Signed-off-by: Stefan Müller-Klieser <s.mueller-klieser@phytec.de>
Diffstat (limited to 'recipes-bsp')
-rw-r--r--recipes-bsp/barebox/env-2015.09.0-phy4/ti33x/commonenv/nv/linux.bootargs.rootfs2
-rw-r--r--recipes-bsp/barebox/env-2015.11.0-phy1/mx6/commonenv/nv/linux.bootargs.rootfs2
2 files changed, 2 insertions, 2 deletions
diff --git a/recipes-bsp/barebox/env-2015.09.0-phy4/ti33x/commonenv/nv/linux.bootargs.rootfs b/recipes-bsp/barebox/env-2015.09.0-phy4/ti33x/commonenv/nv/linux.bootargs.rootfs
index e33ec00..199c7b5 100644
--- a/recipes-bsp/barebox/env-2015.09.0-phy4/ti33x/commonenv/nv/linux.bootargs.rootfs
+++ b/recipes-bsp/barebox/env-2015.09.0-phy4/ti33x/commonenv/nv/linux.bootargs.rootfs
@@ -1 +1 @@
-rootwait ro
+rootwait ro fsck.repair=yes
diff --git a/recipes-bsp/barebox/env-2015.11.0-phy1/mx6/commonenv/nv/linux.bootargs.rootfs b/recipes-bsp/barebox/env-2015.11.0-phy1/mx6/commonenv/nv/linux.bootargs.rootfs
index e33ec00..199c7b5 100644
--- a/recipes-bsp/barebox/env-2015.11.0-phy1/mx6/commonenv/nv/linux.bootargs.rootfs
+++ b/recipes-bsp/barebox/env-2015.11.0-phy1/mx6/commonenv/nv/linux.bootargs.rootfs
@@ -1 +1 @@
-rootwait ro
+rootwait ro fsck.repair=yes