Run fsck to resolve possible data corruption
Trigger fsck on mount of /data if the value of ro.preventative_fsck is not equal to the contents of /metadata/vold/preventative_fsck, then set the file to the property to prevent future runs See b/305658663 for context Bug: 305658663 Test: Make sure fsck run after first boot and not after second Change-Id: I1263d2d55fe22d994ae8c8654b1e75ad9e4ddafe
This commit is contained in:
parent
7b13bc6d5e
commit
1bc693d338
1 changed files with 4 additions and 0 deletions
|
@ -51,3 +51,7 @@ PRODUCT_PRODUCT_PROPERTIES += \
|
||||||
# Set thermal warm reset
|
# Set thermal warm reset
|
||||||
PRODUCT_PRODUCT_PROPERTIES += \
|
PRODUCT_PRODUCT_PROPERTIES += \
|
||||||
ro.thermal_warmreset = true
|
ro.thermal_warmreset = true
|
||||||
|
|
||||||
|
# Trigger fsck on upgrade (305658663)
|
||||||
|
PRODUCT_PRODUCT_PROPERTIES += \
|
||||||
|
ro.preventative_fsck = 1
|
Loading…
Add table
Add a link
Reference in a new issue