summaryrefslogtreecommitdiff
path: root/meta-phosphor/recipes-core/systemd/obmc-targets/obmc-host-reset@.target
diff options
context:
space:
mode:
authorAdriana Kobylak <anoo@us.ibm.com>2020-01-14 18:59:09 +0300
committerBrad Bishop <bradleyb@fuzziesquirrel.com>2020-02-10 22:45:17 +0300
commit81c34d5f701c47059a1c87793f5849bc909d3a75 (patch)
tree8d035a91389556f91fc6958212aac8aa5ce96b99 /meta-phosphor/recipes-core/systemd/obmc-targets/obmc-host-reset@.target
parent0adf892516db0935d11ae7c6f76414ae72ac23aa (diff)
downloadopenbmc-81c34d5f701c47059a1c87793f5849bc909d3a75.tar.xz
preinit-mounts: init: Enhance handling of overlay errors
There has been a couple instances of overlay errors: duplicated overlay mounts, and corrupted files that live in a subdirectory. Add the following enhancements for when an overlay error is detected: - If the etc umount fails, do not attempt to re-mount the overlay. This prevents duplicate mounts. - Check each file after re-creating the overlay, and if it still has errors, delete it from the overlay. This would help also in cases like the point above where the umount fails and the overlay was not recreated. - Check all overlay files recursively instead of just the ones in the top directory. One instance of this corruption was seen on a file in a subdirectory. Tested: Verified the script would check all files in the overlay. (From meta-phosphor rev: 50b569209789f824b7dac8c94adb01b78c0bf3f6) Change-Id: I570a17ec00b7d303abe4654431c0c79d3dd95c1b Signed-off-by: Adriana Kobylak <anoo@us.ibm.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Diffstat (limited to 'meta-phosphor/recipes-core/systemd/obmc-targets/obmc-host-reset@.target')
0 files changed, 0 insertions, 0 deletions