Dapper: persistent boot failure - ext3 filesystem not detected
Bug #37528 reported by
Ulf Karlsson
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
klibc (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Dapper |
Invalid
|
Medium
|
Unassigned |
Bug Description
In the fstype tool there is a problem if the lower 16 bit of number of free inodes in a ext3 filesystem happens to match minix filesystem magic.
This will cause the system not to boot since ubuntu will attempt to mount the filesystem as a minix filesystem.
This problem has been discussed before, but the cause was never investigated, e.g.:
http://
Stupid workaround:
mount /dev/sda1 /root
touch /root/newfile
sync
Changed in klibc: | |
status: | Unconfirmed → Confirmed |
To post a comment you must log in.
Apparently is fixed by:
http:// www.kernel. org/git/ gitweb. cgi?p=libs/ klibc/klibc. git;a=commit; h=2f7cdff4361e6 5c6405a0a0e1736 3e9684567fa0
Which through some unfortunate circumstance does not appear to be in dapper version of klibc..