Jump to content

Welcome to CyanogenMod

Welcome to our forum. Like most online communities you must register to post, but don't worry this is a simple free process that requires minimal information for you to signup. Be a part of the CyanogenMod Forum by signing in or creating an account. You can even sign in with your Facebook or Twitter account.
  • Start new topics and reply to others
  • Subscribe to topics and forums to get automatic updates
  • Get your own profile and make new friends
  • Download files attached to the forum.
  • Customize your experience here
  • Share your CyanogenMod experience!
Guest Message by DevFuse
 

EXT4 mounted as EXT2


  • Please log in to reply
7 replies to this topic

#1 mmorselli

mmorselli
  • Members
  • 21 posts
  • Country:
    it - Italy
  • Device Model:
    HTC Desire | Galaxy TAB
  • CM Version:
    CM7.1
  • Recovery Image:
    ClockworkMod

Posted 23 February 2011 - 08:54 PM

Maybe a FAQ, but search didn't help me.

Cyanogen 7 RC1, EXT4 formatted /ext partition on SD-CARD.

Via ADB SHELL, mount reports:

/dev/block/mmcblk0p2 on /sd-ext type ext2 (rw,noatime,nodiratime,barrier=1,data=ordered)

via recovery (clockwork 3.0.0.5) mount reports:

/dev/block/mmcblk0p2 on /sd-ext type ext2 (rw,relatime,barrier=1,data=ordered)

via recovery (Amon RA 2.0.0)

/dev/block/mmcblk0p2 on /sd-ext type ext4 (rw,nodev,noatime,nodiratime,barrier=1,data=ordered)


Why ext4 is mounted only via Amon RA recovery?

#2 mmorselli

mmorselli
  • Members
  • 21 posts
  • Country:
    it - Italy
  • Device Model:
    HTC Desire | Galaxy TAB
  • CM Version:
    CM7.1
  • Recovery Image:
    ClockworkMod

Posted 27 February 2011 - 10:01 PM

If none of developers can explain it, someone may at least tell me if anybody have the same situation or the issue are only on my system?

Tnks in advance.

#3 mercuryy

mercuryy
  • Members
  • 32 posts
  • Country:
    de - Germany
  • Device Model:
    Desire
  • CM Version:
    7
  • Recovery Image:
    ClockworkMod

Posted 27 February 2011 - 10:23 PM

Might depend on the fstab used, or on the availiability of ext4 kernel modules in the different environments you are in..

#4 mmorselli

mmorselli
  • Members
  • 21 posts
  • Country:
    it - Italy
  • Device Model:
    HTC Desire | Galaxy TAB
  • CM Version:
    CM7.1
  • Recovery Image:
    ClockworkMod

Posted 28 February 2011 - 10:16 PM

cat /system/etc/vold.fstab

## Vold 2.0 fstab for HTC Bravo
#
## - San Mehat (san@[email protected])
##

#######################
## Regular device mount
##
## Format: dev_mount <label> <mount_point> <part> <sysfs_path1...>
## label		- Label for the volume
## mount_point  - Where the volume will be mounted
## part		 - Partition # (1 based), or 'auto' for first usable partition.
## <sysfs_path> - List of sysfs paths to source devices
######################

# Mounts the first usable partition of the specified device
dev_mount sdcard /mnt/sdcard auto /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.2/mmc_host/mmc1

#

hboot is the alpharev patched for cyanogen7, but for kernel modules, I'm wrong supposing that all Cyanogen 7 RC1 have the same?

#5 kkoolpatz

kkoolpatz
  • Members
  • 5 posts

Posted 02 March 2011 - 07:26 PM

View Postmmorselli, on 27 February 2011 - 10:01 PM, said:

If none of developers can explain it, someone may at least tell me if anybody have the same situation or the issue are only on my system?

Tnks in advance.


Not sure why, but if thats a problem for you, you can write a script to mount mmcblk*'s manually in the init.d


BUSYBOX="/system/xbin/busybox"
$BUSYBOX mkdir /mnt/your_dir
/system/bin/tune2fs -l /dev/block/mmcblk0p2
$BUSYBOX mount -t ext4 -o noauto_da_alloc,commit=15,barrier=0,nobh,nouser_xattr,errors=continue,noatime,nodiratime,nosuid,nodev /dev/block/mmcblk0p2 /mnt/your_dir
$BUSYBOX chown 1000.1000 /mnt/your_dir
$BUSYBOX chmod 771 /mnt/your_dir

Alternatively try using mount -t auto -o your_options.

#6 mmorselli

mmorselli
  • Members
  • 21 posts
  • Country:
    it - Italy
  • Device Model:
    HTC Desire | Galaxy TAB
  • CM Version:
    CM7.1
  • Recovery Image:
    ClockworkMod

Posted 02 March 2011 - 09:57 PM

thank you very much kkoolpatz, thanks to your hints I have change /system/bin/launcha2sd (DarkTremor AP2SD) from

$bbmount -o noatime,nodiratime -t auto $a2sdblk $mntpoint | $tee

to

$bbmount -o noauto_da_alloc,commit=15,barrier=0,nobh,nouser_xattr,errors=continue,noatime,nodiratime,nosuid,nodev -t ext4 $a2sdblk $mntpoint | $tee

and now my /sd-ext is mounted as EXT4


$bbmount is an alias for busybox mount, so the error of -t auto maybe was related to busybox, and not cyanogen ? Or both?

Edited by mmorselli, 02 March 2011 - 09:57 PM.


#7 kkoolpatz

kkoolpatz
  • Members
  • 5 posts

Posted 03 March 2011 - 07:01 PM

Quote


$bbmount is an alias for busybox mount, so the error of -t auto maybe was related to busybox, and not cyanogen ? Or both?

Its most likely a limitation of busybox. because cyanogenmod is just outer clothes, everything else is basically common to all android OS. Also that could be the reason why all of the mounters except amon ra mounted is as ext2.  Did you use the same code while mounting using amon ra? i have never used amod ra so not sure if it uses its own mounting utils or relies on busybox...

#8 catzilla

catzilla
  • Donators
  • 161 posts
  • Country:
    us - United States
  • Device Model:
    i747 (d2att)
  • CM Version:
    CM10
  • Recovery Image:
    ClockworkMod

Posted 15 March 2011 - 07:01 PM

kkoolpatz, mmorselli, thank you so much!

I've been looking around for a way to actually mount the ext partition as ext4, the ext2 mount bug has been bugging me for about two months!

Edited by catzilla, 15 March 2011 - 07:03 PM.