Revert "flo: fstab latemount cache too"

* This caused numerous issues. The biggest of which being that /cache's
  block device was labeled incorrectly as it was latemounted. Due to
  this, Lineage Updater would fail to write to /cache directories for
  updates, causing them to fail.

* Lesson learned, several optimizations Google included on the Pixel's
  won't work/aren't feasible on non-A/B devices.

This reverts commit ed5a9106b1dfcfa1f1790d68e49bfc1d17e285f6.

Change-Id: I21f277c6888e06453866b8fd99004f38dce07ebb
This commit is contained in:
Nolen Johnson 2018-06-13 09:21:39 -04:00 committed by followmsi
parent 11cdaa374f
commit 1b44da642f
1 changed files with 2 additions and 2 deletions

View File

@ -4,8 +4,8 @@
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,barrier=1 wait,first_stage_mount
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 noatime,nosuid,nodev,barrier=1,data=ordered,noauto_da_alloc,errors=panic latemount,wait,check,formattable
/dev/block/platform/msm_sdcc.1/by-name/cache /cache f2fs rw,nosuid,nodev,noatime,inline_xattr latemount,wait,check,formattable
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 noatime,nosuid,nodev,barrier=1,data=ordered,noauto_da_alloc,errors=panic wait,check,formattable
/dev/block/platform/msm_sdcc.1/by-name/cache /cache f2fs rw,nosuid,nodev,noatime,inline_xattr wait,check,formattable
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 noatime,nosuid,nodev,barrier=1,data=ordered,noauto_da_alloc,errors=panic latemount,wait,check,formattable,encryptable=/dev/block/platform/msm_sdcc.1/by-name/metadata
/dev/block/platform/msm_sdcc.1/by-name/userdata /data f2fs rw,nosuid,nodev,noatime,inline_xattr latemount,wait,check,formattable,encryptable=/dev/block/platform/msm_sdcc.1/by-name/metadata
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 noatime,nosuid,nodev,barrier=1,data=ordered,nodelalloc wait