Previously on Oxygen OS 4.5.15 running your /data partition on F2FS had no problems.
However currently if you try running your /data partition with F2FS either you get an infinite boot loop or if you're decrypted you get an error message that says "Encryption unsuccessful" I'm assuming that's just the kernel being unable to mount the /data partition and just assuming it was a bad encryption or corrupted partition message.
Default partition layout for /data seems to be EXT4 and that works correctly just posting a new topic here to see if anyone else knows the status of F2FS was it removed form OxygenOS 5 kernel?
vortex-5 said:
Previously on Oxygen OS 4.5.15 running your /data partition on F2FS had no problems.
However currently if you try running your /data partition with F2FS either you get an infinite boot loop or if you're decrypted you get an error message that says "Encryption unsuccessful" I'm assuming that's just the kernel being unable to mount the /data partition and just assuming it was a bad encryption or corrupted partition message.
Default partition layout for /data seems to be EXT4 and that works correctly just posting a new topic here to see if anyone else knows the status of F2FS was it removed form OxygenOS 5 kernel?
Click to expand...
Click to collapse
By default, OxygenOS (OOS) comes with File Based Encryption (FBE) enabled. FBE, at present, is not compatible with F2FS and hence OnePlus has the /data partition defaulting to EXT4.
If you wish to use F2FS on /data, you'd need to be decrypted, a. and b. you'd need a kernel that supports booting with F2FS as well. Also, I'm not sure but I think the latest TWRPs for OP5 also don't have the necessary stuff to convert the filesystem to F2FS, but I haven't checked that myself, so can't say that with certainty.
Related
Hello,
I'm a new developer and try to reference other people's steps to change /data to f2fs. However, I have some problems and it have bothered me a few days. When I chose format /data and type yes, it showed error message " E: Unable to mount '/data' ". As a result, I decided to format then mount /data by myself. Unfortunately, when I used modified TWRP to mount /data which have already formatted by mkfs.f2fs , it showed error message "mounting /data, operation not supported on transport endpoint". However when I mount /data which formatted by make_ext4, it was success. I have already read my threads but I couldn't find a solution. Did any thing I forget to modified? Can anyone help me or give me some hints? Plz
Here is my modify step: (reference ss2man44 's thread in Nexus 7 Developer Discussion ,＃Use of F2FS for /data)
1. use f2fs patch to modified kernel, turn on f2fs then flash to my device. It works.
2. modified twrp.fstab and fstab.grouper
3. give statically link to TWRP
Here is my environment:
Device: Nexus 7 (2012)
Kernel version: 3.1.10 (nightly)
Android version: 4.4.3
ROM: CyanogenMod(cm-11)
TWRP: 2.7.1.0 (support F2FS)
CONFIG_F2FS_FS=y
CONFIG_F2FS_STAT_FS=y
CONFIG_F2FS_FS_XATTR=y
CONFIG_F2FS_FS_POSIX_ACL=y
CONFIG_F2FS_FS_SECURITY=y
That last one defaults to N.
Switching to y fixes f2fs in twrp. However, it looks like I'm running into additional selinux issues with android: ubject_r:unlabeled:s0 data
There seems to be a lot of confusion or pr people aren't being clear enough. At the moment there's one build found here http://forum.xda-developers.com/showpost.php?p=65193930&postcount=1302 that has F2FS as an option to change to. But I recall there being a problem with the /cache partition too small for F2FS to work, and if you look into F2FS's internal operation a bit, if /cache isn't F2FS then it's pointless.
So I'm asking, is there any TWRP build that supports formatting system/cache/data partitions as F2FS? Is there a way to fix whatever the problem is with /cache unable to be formatted to F2FS? The error I get when I try to format with F2FS is this:
Code:
mkfs.f2fs -t 0 /dev/block/mmcblk0p38 process ended with error: 255
Unable to WIpe Cache
Error changing file system.
Do we need ROM/kernel makers to specifically make their projects with F2FS support? What is the technical issue with getting /cache formatted as F2FS?
bobbarker2 said:
There seems to be a lot of confusion or pr people aren't being clear enough. At the moment there's one build found here http://forum.xda-developers.com/showpost.php?p=65193930&postcount=1302 that has F2FS as an option to change to. But I recall there being a problem with the /cache partition too small for F2FS to work, and if you look into F2FS's internal operation a bit, if /cache isn't F2FS then it's pointless.
So I'm asking, is there any TWRP build that supports formatting system/cache/data partitions as F2FS? Is there a way to fix whatever the problem is with /cache unable to be formatted to F2FS? The error I get when I try to format with F2FS is this:
Code:
mkfs.f2fs -t 0 /dev/block/mmcblk0p38 process ended with error: 255
Unable to WIpe Cache
Error changing file system.
Do we need ROM/kernel makers to specifically make their projects with F2FS support? What is the technical issue with getting /cache formatted as F2FS?
Click to expand...
Click to collapse
Old post, but F2FS requires a minimum of 100 MB to be used on a drive. Ours is 99 MB.
i'm on latest open beta 7(8.1) on my oneplus 5. i just unlocked the bootloader and flashed the bluespark twrp then i tried to change the system partition file system as f2fs. it showing done but on next line it showing an error as failed to mount '/system'(no such device). i tried official twrp also and facing the same error. it changed to f2fs but after booting it was again changed to ext4(checked with diskinfo)
then i can't able to mount the system also
Please help to solve this error and to change the file system as f2fs.
i can't able to boot into system on ob7 with twrp. but can be booted with stock recovery. please help me thanks in advance.
Ragavendran 007 said:
i'm on latest open beta 7(8.1) on my oneplus 5. i just unlocked the bootloader and flashed the bluespark twrp then i tried to change the system partition file system as f2fs. it showing done but on next line it showing an error as failed to mount '/system'(no such device). i tried official twrp also and facing the same error. it changed to f2fs but after booting it was again changed to ext4(checked with diskinfo)
then i can't able to mount the system also
Please help to solve this error and to change the file system as f2fs.
i can't able to boot into system on ob7 with twrp. but can be booted with stock recovery. please help me thanks in advance.
Click to expand...
Click to collapse
You have to format data and then change system partition to ext4 and now you can flash the rom again.
Aarju said:
You have to format data and then change system partition to ext4 and now you can flash the rom again.
Click to expand...
Click to collapse
I formatted the data . Then only I tried to change the file system as f2fs. .. I want to change the filesystem as f2fs
Ragavendran 007 said:
I formatted the data . Then only I tried to change the file system as f2fs. .. I want to change the filesystem as f2fs
Click to expand...
Click to collapse
Ext4 is better than f2fs and also you have to first format again and then clean flash is required.
Aarju said:
Ext4 is better than f2fs and also you have to first format again and then clean flash is required.
Click to expand...
Click to collapse
F2fs has better writing speed. Then I may help to install the apps faster.. right?
https://medium.com/thecyberfibre/f2fs-versus-ext4-our-take-on-the-ongoing-battle-c0324f46d040
Ragavendran 007 said:
F2fs has better writing speed. Then I may help to install the apps faster.. right?
Click to expand...
Click to collapse
While faster, you may find yourself with compatibility issues in regard to your preferred ROM, etc.
Sticking with ext4 (for now) is simply the better option at the moment because it ensures that your reliability and compatibility. Also, there are apparently some issues with f2fs when it comes to device encryption.
Therefore: just wait. Maybe in the future f2fs will be the better option. As for now: I don't think that with an OP5 you need to worry about the installation time of apps taking too long.
I've unlocked my new MI9T to install xiaomi.eu rom.
First of all, after unlock, i've installed the official TWRP and i've formatted (not wiped) the DATA partition.
I've noticed that TWRP logged that it was formatting the DATA partition with mkfs.f2fs ...... really strange...
So, i've rebooted to TWRP and changed the DATA partition type to EXT4 and formatted it... after a reboot i've tried to format it again and it was formatted again in F2FS (like F2FS was the default selection).
So i've tried to switch to OrangeFox recovery (i suspected a bug in TWRP)... but the same behaviour...seems that F2FS is the default partition type for my DATA partition.
I've installed the xiaomi.eu (the kernel in this rom is the official one, and i dont think that it supports F2FS) and the rom boot ok, without problems.
I've tried also to force ext4 on DATA, but with this partition type the rom never boot (it remains on the android bootanimation).
So right now, i see a f2fs partition type on my data partition, with original kernel.
I've tried also to change the cache partition to f2fs (by default this partition is formatted in ext4) but in this way, the rom boots, but i can't see the cache partition, seems that effectively the kernel can't mount the cache partition.
so i've unpacked the official miui_DAVINCIEEAGlobal_V11.0.4.0.QFJEUXM_5001481fbb_10.0 rom, and i've found that in the vendor partition, under (vendor)/etc/fstab.qcom there is this entry for DATA partition:
Code:
/dev/block/bootdevice/by-name/userdata /data [B]f2fs [/B]noatime,nosuid,nodev,nodiscard,fsync_mode=nobarrier,reserve_root=32768,resgid=1065 wait,check,fileencryption=ice,wrappedkey,quota,reservedsize=128M,latemount
So, this phone uses by default a F2FS partition type for DATA????
gulp79 said:
...so i've unpacked the official miui_DAVINCIEEAGlobal_V11.0.4.0.QFJEUXM_5001481fbb_10.0 rom, and i've found that in the vendor partition, under (vendor)/etc/fstab.qcom there is this entry for DATA partition:
So, this phone uses by default a F2FS partition type for DATA????
Click to expand...
Click to collapse
Yes - stock QFJEUXM 11.0.4, never formatted (or wiped) Data, see screenshot from /vendor/etc/fstab.qcom
setting fileencrypt=ice under fstab mount flags for a F2FS formatted /data partition causes the phone to boot into fastboot mode. why is that? it works fine with EXT4 though. my rom's kernel got built in F2FS. ?