summaryrefslogtreecommitdiff
path: root/fstab.common
diff options
context:
space:
mode:
authorJohn Stultz <john.stultz@linaro.org>2020-03-12 05:26:07 +0000
committerJohn Stultz <john.stultz@linaro.org>2020-03-16 22:59:46 +0000
commit650d7b54409a4ef627428f06bf41d2b0d09961b4 (patch)
tree19857a52bb11de645de8a45d7458d78369d0dab5 /fstab.common
parentbd4744f89b5d70dea0db526278b7d3ac393fd098 (diff)
db845c: Make userdata formattable
If one runs "fastboot erase userdata", and then does not flash a userdata image to the partition, the system will fail to boot as /data/ will not mount, and the apex and dalvik cache directories won't be present or writable. This tries to address this by adding the formattable flag to the fstab and add the partition to the sepolicy so mkfs can access it. NOTE: I did have to use the full by-name path in the fstab, which is less flexible then the LABEL= method, but if the partition isn't formatted there isn't neceessarily a partition label to find. Big thanks to AmitP for suggesting this approach Signed-off-by: John Stultz <john.stultz@linaro.org> Change-Id: Ia678d0d1d5e1eb35462f8fcfee478969c614b0d4
Diffstat (limited to 'fstab.common')
-rw-r--r--fstab.common2
1 files changed, 1 insertions, 1 deletions
diff --git a/fstab.common b/fstab.common
index 7ccfed5..ad29337 100644
--- a/fstab.common
+++ b/fstab.common
@@ -2,5 +2,5 @@
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
-LABEL=data /data ext4 discard,noauto_da_alloc,data=ordered,user_xattr,barrier=1 wait
+/dev/block/platform/soc@0/1d84000.ufshc/by-name/userdata /data ext4 discard,noauto_da_alloc,data=ordered,user_xattr,barrier=1 wait,formattable
/dev/block/by-name/metadata /metadata ext4 noatime,nosuid,nodev,discard wait,formattable