device_google_zuma/conf/init.efs.4k.rc at c7a783220ebfdc8f33d76c7f5a596e11d1c93e02 - Evolution-X-Tensor/device_google_zuma - Forgejo: Beyond coding. We Forge.

Evolution-X-Tensor/device_google_zuma

Kelvin Zhang b08f8dbf23 Reland: Copy files on EFS partition to /data on boot

During boot, this CL adds the following sequence of actions:

1. mount original efs partitions(most likely f2fs) on /mnt/vendor/efs
2. copy files in /mnt/vendor/efs to /data/vendor/copied/efs.img
3. fsync all the files in /data/vendor/copied/efs.img
4. rename /data/vendor/copied/efs.img to /data/vendor/copied/efs
5. bind-mount /data/vendor/copied/efs to /mnt/vendor/efs
6. repeat 1-5 for efs_backup and modem_userdata

The original EFS partitions are mounted and only used for file
copying, no destructive action done on original efs partitions.

Test: reformat /data as ext4, boot the device
Bug: 319335586
Change-Id: Ide78be316778acfc5c582c4a7b78853796cf4c1e

2024-05-07 21:31:13 -07:00

4 lines

137 B

Text

Raw Blame History

 on post-fs-data
     mount_all /vendor/etc/fstab.efs
     mount_all /vendor/etc/fstab.persist
     setprop ro.vendor.persist.status mounted