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:1bc693d338e8d26307d51bb6731d8e94f1df33f9)
Merged-In: I1263d2d55fe22d994ae8c8654b1e75ad9e4ddafe
Change-Id: I1263d2d55fe22d994ae8c8654b1e75ad9e4ddafe
This commit is contained in:
Paul Lawrence 2023-10-24 07:59:40 -07:00 committed by Android Build Coastguard Worker
parent 9652836b87
commit 9f697c42f5

View file

@ -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