maemo.org Bugzilla – Bug 3852
Boot from mmc/usb: root ext3 filesystem gets mounted as ext2
Last modified: 2010-02-14 14:38:24 UTC
You need to
before you can comment on or make changes to this bug.
(Control Panel > General > About product)
STEPS TO REPRODUCE THE PROBLEM:
Make a ext3 partition on one of the mmc cards and clone system into it.
Configure tablet to boot from mmc
Boot and check the mounted filesystems
/ mounted as ext3
/ mounted as ext2
EXTRA SOFTWARE INSTALLED:
none that matters, it is a initfs issue
filesystem modules are inserted in wrong order in linuxrc, if ext2.ko is
inserted before ext3.ko, /proc/filesystems will show ext2 before ext3, then
busybox's mount will probe ext2 before ext3 and mount any ext3 filesystem as
To avoid that, ext3.ko must be inserted before ext2.ko
Line 10 of linuxrc should read:
FS_MOUDLES="mbcache jdb ext3 ext2"
User-Agent: Mozilla/5.0 (compatible; Konqueror/3.5) KHTML/3.5.9 (like
ext3 file systems are also valid ext2 file system, while it's not the other way
round. Hence a valid request.
Current state of /mnt/initfs/linuxrc in 4.2008.36-5:
FS_MODULES="mbcache ext2 jbd ext3"
the internal copy of this bug was closed as invalid because
"When mounting, you may always specify '-t ext3' parameter. You should dig the
initfs script which is doing the mounting and add '-t ext3' there. Relaying on
module insertion order is fundamentally wrong."
No comments here for two weeks, hence closing as INVALID too.
What is fundamentally wrong then is busybox's mount, because it relies on
module order to autodetect the filesystem type.
Changing linuxrc to "mount -t ext3" will have the effect that when inserting an
ext2 formatted mmc, then it will be unable to automount it, and won't be able
to boot from it.
Marking patches of interest to Diablo (Maemo4) community updates, please excuse