Hi,
I am now using F2FS for the data and cache partitions of my Nexus 5.
my kernel is blu_sp★rk r56
my rom is Cataclysm
Everything is OK and my Nexus 5 is snappier!
BUT, from time to time, the /data partition becomes read only... which causes the crash of lots of applications. Most of the time, this happens during the night and I notice it on the morning. This never happened when the /data partition was ext4.
What could be the cause of this problem? How to investigate it?
Thanks in advance for your help !
Phyl
Related
Rather than making a loopback filesystem, I've been trying to reformat the data partition as ext4, but haven't been able get past the galaxy "S" screen yet (the big S on boot). Here's what I did
* Compile a kernel with ext4 and modified init.rc to mount /data as ext4.
* Reboot into recovery and format /dev/block/mmcblk0p2 as ext4.
* Reboot into download and flash the custom kernel.
It was stuck at "S" for a while, then the screen went dark, and the only thing I could do was to pull out the battery. Then I went into recovery mode and found the partition was trashed, i.e. I couldn't mount it as ext4 again. I had to format it back to rfs and restore the stock kernel to get it to boot. I have to believe that there's something other than init.rc that assumes data partition to be in a certain format. Has anyone had success on a similar task?
BTW, the same process DID work for /dbdata, but I see no visible improvement in Quadrant score...
I has a similar thing occur on my first attempt with nilfs2. Did you remove anything that would attempt to mount as rfs? I think the rfs driver will claim pretty much anything that might be rfs, so if your format left the backup FAT intact, that might be your problem. By the way, the nilfs2+user_init kernel I posted in the mimocan fix thread does support ext4 as well, and allows you to customize the mount without rebuilding your kernel.
Sent from my SAMSUNG-SGH-I897 using XDA App
Hello,
i am using lagfix on my nexus s. But by default , only /data partition is selected for trim command.
Can i check /system and trim it also safely without bricking or any other issues?
secondly.. the /cache partition is disabled altogether.. and i get a prompt that the /cache partition isnt supported due to hardware or due to the limitations of the kernel on the device. So my query.. whats the limititation? the h/w or the default cm10 kernel? is there a kernel that i can use so as to get trim to run on /cache partition? is it possible..
please share your opinion.
my nexus s seems to start lagging a lot . i want to bring it back to life.. any proven suggestions would be appreciated.
Thanks so much XDA community.
i wanted to know if it is possible to format our system partition as f2fs and have it work our data partition on kitkat is already f2fs so are we able to do it to system? in twrp i attempted this by fro matting to f2fs but when restoring system it reformats system as ext 4 is there away around this? on twrps website there is a command to keep a the file system it is "tw_rm_rf – uses rm –rf instead of formatting system and data partitions, this option is used to prevent changes to the file system settings such as file system type, " i found it here http://www.teamw.in/twrp2-reference-guide would this help to do this? i don't know where to put this command in though
Edit: on a sidenote i formatted cache as f2fs and it booted
Edit 2: i looked at it again and cache was reformatted back to ext4
billycar11 said:
i wanted to know if it is possible to format our system partition as f2fs and have it work our data partition on kitkat is already f2fs so are we able to do it to system? in twrp i attempted this by fro matting to f2fs but when restoring system it reformats system as ext 4 is there away around this? on twrps website there is a command to keep a the file system it is "tw_rm_rf – uses rm –rf instead of formatting system and data partitions, this option is used to prevent changes to the file system settings such as file system type, " i found it here http://www.teamw.in/twrp2-reference-guide would this help to do this? i don't know where to put this command in though
Edit: on a sidenote i formatted cache as f2fs and it booted
Edit 2: i looked at it again and cache was reformatted back to ext4
Click to expand...
Click to collapse
Did you ever succeed in getting stock "DATA" partition to F2FS? I couldn't restore my backup and phone wouldn't boot anymore.. so went back to EXT4..
Maybe @djvita knows something, I think he has been experimenting a bit with F2FS..
StefanGA said:
Did you ever succeed in getting stock "DATA" partition to F2FS? I couldn't restore my backup and phone wouldn't boot anymore.. so went back to EXT4..
Maybe @djvita knows something, I think he has been experimenting a bit with F2FS..
Click to expand...
Click to collapse
yes i was able to get only the data partition to f2fs no other partition will stay another format once it boots it reformats or when restoring system in twrp it will restore the system partition as ext 4
billycar11 said:
yes i was able to get only the data partition to f2fs no other partition will stay another format once it boots it reformats or when restoring system in twrp it will restore the system partition as ext 4
Click to expand...
Click to collapse
interesting.. how did you do it? I did it in TWRP 2.8.1.0 via advanced wipe and after that got stuck on the motorola bootlogo..
That is the same thing I did but after whipeing I restored my data partition. I think the reason you got stuck in a bootloop is because you did not clear dalvic and cache or you do not have the kit Kat boot loader
billycar11 said:
That is the same thing I did but after whipeing I restored my data partition. I think the reason you got stuck in a bootloop is because you did not clear dalvic and cache or you do not have the kit Kat boot loader
Click to expand...
Click to collapse
I tried it again.. this time it worked.. I rebooted after format directly back into recovery and was then able to restore my data from ext4 to f2fs.. not sure, why it didn't work the first time around, but thanks for checking back!
i was reading the temasek thread and noticed that keeping /system on ext4 is better for the phone. judging by the slow downs i found after switching to f2fs... i have to agree. so i am hoping to clarify something right quick. formatting /system back to ext4 - will not erase my roms, correct? thanks.
phermey said:
i was reading the temasek thread and noticed that keeping /system on ext4 is better for the phone. judging by the slow downs i found after switching to f2fs... i have to agree. so i am hoping to clarify something right quick. formatting /system back to ext4 - will not erase my roms, correct? thanks.
Click to expand...
Click to collapse
Formatting /system will erase everything that resides in the /system partition obviously.
timmaaa said:
Formatting /system will erase everything that resides in the /system partition obviously.
Click to expand...
Click to collapse
indeed obviously. i have so many issues with the drivers on my xp machine that i just wanted to be sure. if it erased my downloads... i would have been hours. i went ahead and took the chance a bit earlier. i should have updated. thanks for responding.
Hi all! I'm running CM13 Snapshot, with ElementalX. As now I formatted /data and /cache in F2FS. Would it be worth to also format /system in F2FS, since is mostly read-only?
Well you simply can't, every ROM installation will re-format /system to ext4 automatically. And even if you could, you probably can't notice any improvements on the Nexus 5. The Nexus 5 still has pretty powerful hardware which can handle almost everything without any problems so I wonder why you would want to have /system formatted to F2FS. In my experience things never really got that much better with the /cache and /data formatted to F2FS, only benchmarks scores got a bit higher. In my opinion F2FS is pretty useless on this device. Could be helpful for lower end ones.
Thanks for the answer! I must say i jumped on the f2fs train without doing any benchmarks, and also going from KK to LP long time ago, so I couldn't do a proprer comparison. Also I didn't think about the rom installation process reformatting...well than my question is pretty useless
Short answer, no. From what I've read, F2FS has slightly better write speeds than ext4 and slightly worse read speed. On a partition that you write often to, such as data and cache, it could be beneficial because of the better write speed. But on the system partition, it would even cause performance drop since it's read-only.
No.
The system partition is mounted mostly with ro permissions anyway.
Write operations are few and rare.
Finally, f2fs seems to have more overhead (allocates more space) which might be an issue for devices with small-ish system partitions.