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 (cherry picked from https://googleplex-android-review.googlesource.com/q/commit:e4a81c0e8f9f8d89f0e42e8fd7ec40cec6b887ed) Merged-In: I1263d2d55fe22d994ae8c8654b1e75ad9e4ddafe Change-Id: I1263d2d55fe22d994ae8c8654b1e75ad9e4ddafe
This commit is contained in:
parent
2097946299
commit
fbfc56b8aa
1 changed files with 4 additions and 0 deletions
|
@ -48,3 +48,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