#11018 NORM 11.2.0-: /bootpart not mounted after activation
Zarro Boogs per Child
bugtracker at laptop.org
Fri Jun 24 13:13:29 EDT 2011
#11018: /bootpart not mounted after activation
-----------------------+----------------------------------------------------
Reporter: dsd | Owner: dsd
Type: defect | Status: new
Priority: normal | Milestone: 11.2.0-final
Component: initramfs | Version: not specified
Keywords: | Next_action: never set
Verified: 0 | Deployment_affected:
Blockedby: | Blocking:
-----------------------+----------------------------------------------------
After activating the laptop, it boots directly but /bootpart cannot be
mounted.
This is because (in this scenario), /security was mounted off that same
partition as ext4 by the initramfs, and olpc-configure then tries to mount
/bootpart as ext2 (via mount, which tries the filesystems listed in
/etc/filesystems, as ext2 comes first).
mount returns EBUSY here, thinking that ext2 is different from ext4,
preventing you from mounting the same partition twice but using 2
different fs drivers (in this case, the drivers are the same - we build
the ext4 driver also operating under the ext2 and ext3 names)
In non-activation boot mode, the runrd initramfs mounts /security as ext2,
meaning that /bootpart can then also be mounted as ext2 without problem.
The reason for the difference is that /etc/filesystems is present in the
activation initramfs (but not the runrd) with contents:
{{{
vfat
ext4
ext3
ext2
}}}
(purpose: autoload the vfat kernel module when trying to mount usb disks
looking for lease.sig)
The /security mount that happens after activation then also uses this
file, preferring ext4 (because its at the top of the list), leading to the
described situation.
This is a regression over 10.1.3. Impact is that olpc-update would get
confused if being run on a boot when activation has just happened.
--
Ticket URL: <http://dev.laptop.org/ticket/11018>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system
More information about the Bugs
mailing list