[LG Optimus 2x] sugardad:
I just got back from work and was surprised with a finding..

Yesterday after flashing the latest Kernel and posting my mounts output I have loaded my Bro's Device with all his stuff...

So far so good

Today as I said he had some Issues, some tiny lagging and a not so good battery life as In TestBuild 2..

The device was not as full of apps as in other times but what the heck I did my checks and amongst them was the mounts/fs check...

my current mounts/fs check now shows the following ...

# cat /proc/mounts
cat /proc/mounts
rootfs / rootfs ro,noatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,noatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,noatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p1 /system ext4 ro,nodev,noatime,nodiratime,barrier=1,data=ord
ered 0 0
/dev/block/mmcblk0p8 /data ext4 rw,nosuid,nodev,noatime,nodiratime,barrier=1,dat
a=ordered 0 0
/dev/block/mmcblk0p2 /cache ext4 rw,nosuid,nodev,noatime,nodiratime,barrier=1,da
ta=ordered 0 0
tmpfs /mnt/extasec tmpfs rw,nodev,noatime,mode=755,gid=1000 0 0
/dev/block/mmcblk0p6 /lgdrm ext3 rw,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/vold/179:9 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,noatime,ui
d=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=
iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:9 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,noati
me,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocha
rset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/vold/179:17 /mnt/sdcard/_ExternalSD vfat rw,dirsync,nosuid,nodev,noex
ec,noatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp4
37,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:17 /mnt/extsecure/extasec vfat rw,dirsync,nosuid,nodev,noexe
c,noatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp43
7,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/_ExternalSD/.android_secure tmpfs ro,relatime,size=0k,mode=000
0 0

as you can see It shows now as Ext4(!)

I don;t know what triggered this and I cannot understand If this was done by a process that slowly converts the FS

One thing I know and Is for sure

Ext4 wears the Flash faster thus I dislike it, A LOT!

Our Device came originally with Ext3 and Is not meant to work with Ext4 in contrast to Devices that were originally shipped with Ext4 (e.g. Nexus S)

Fact is, devices that ship with Ext4 FS have built-in hardware wear leveling

Most Devices with flash storage that originally ships with ext4 (e.g. Nexus S) come with hardware wear leveling, but if a target device (O2x in this case) originally ships with other file systems that does not do wear leveling, they might not have hardware wear leveling. On these file systems, you might need additional steps to ensure that a lower level driver (e.g. STL) do software wear leveling if you want to safely install ext4.

I'm not saying that going to Ext4 will unleash green dragons and burn your city or your O2x will be covered in flames asking for mercy until It turns to ashes, I'm saying that I dislike Ext4 on unsupported hardware/unoptimized hardware.

I'm reverting back ASAP!

Edit

Here's and Interesting Thread