mirror of
https://github.com/Evolution-X-Devices/device_google_zuma
synced 2026-02-01 07:40:34 +00:00
b08f8dbf23
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
9 lines
480 B
Plaintext
9 lines
480 B
Plaintext
# Android fstab file.
|
|
# <src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
|
|
# Create the specific fstab file for efs partitions for flexibility
|
|
/data/vendor/copied/efs /mnt/vendor/efs none bind latemount
|
|
|
|
/data/vendor/copied/efs_backup /mnt/vendor/efs_backup none bind latemount
|
|
|
|
/data/vendor/copied/modem_userdata /mnt/vendor/modem_userdata none bind latemount
|