Database Users

[Q] make /data to f2fs problem, help !!

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

Moving on to F2FS

My Idea is to change the Filesystem on my d802.
Via adb I pulled the whole /data/media partion so that I can Push it back later.
I am not really Sure how this will work with the System partition.
I believe that flashing a cloudy G3 rom will Format the System partition back to ext4 (i think it's in the install Script).
So Would it be possible that I remove that "formating System" line to keep f2fs. Any other thoughts on this?

Is there a TWRP build that supports F2FS for /system /cache /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.

Mi a1 unmounted /system and /data fs

My Mi A1 device is in a state that is stuck in the first logo boot screen and when I boot into twrp I get errors of failing to mount /system and /data. I have tried the methods of wiping the partitions through twrp but the proccess fails. I have also tried to switch the filesystem to something else but that proccess fail too. Is there a way I could create them from scratch via the terminal in twrp? I don't have the knowledge to do things like that in filesystems and my device is for me right now in a bricked state because of that. Any help would be greatly appreciated.
When I do the switch file system option of /system and /data from twrp i get the error 'E:recv error on uevent'
When I try to do a format I get the errors: 'Could not mount /data and unable to find crypto footer.'
'Unable to mount /data (Invalid Argument)'
'Unable to mount /system (Invalid Argument)'

Hey, have you got any solution for the problem because I have stucked in the same problem. If you got the solution please tell me.

TWRP 0mb of internal storage

Already tried to Format Data, Repair File System and Change File System (to EXT2 then EXT4). It always shows "Failed to mount '/data' (Device or resource busy).
I appreciate any help.

heitormvl said:
Already tried to Format Data, Repair File System and Change File System (to EXT2 then EXT4). It always shows "Failed to mount '/data' (Device or resource busy).
I appreciate any help.
Click to expand...
Click to collapse
Flashing the DM Verity file should fix this for you.

SteveMurphy said:
Flashing the DM Verity file should fix this for you.
Click to expand...
Click to collapse
How do I do that?

I managed to fix it by flashing the official system on it with Odin and then installing a Custom ROM with TWRP.