fstype error causes the root filesystem to not mount
Bug #76675 reported by
hads
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
klibc (Ubuntu) |
Fix Released
|
Critical
|
Colin Watson |
Bug Description
Running Feisty current as of now.
After the update to klibc-utils 1.4.30-3ubuntu1 the fstype binary no longer works.
root@snowman:~# /usr/lib/
stdin: error 0
This then causes any initramfs generated to not know the root filesystem type and therefore not boot.
More specifically, on line 53 of the initramfs copy of /usr/share/
Related branches
Changed in klibc: | |
assignee: | nobody → kamion |
importance: | Undecided → Critical |
status: | Unconfirmed → Confirmed |
To post a comment you must log in.
I'm pretty sure that the problem here is that klibc's internal sys/types.h does "typedef __kernel_loff_t off_t;" (sic), whereas debian/ patches/ 10-use- exported- kernel- headers. patch backs this out in favour of <linux/types.h> which does "typedef __kernel_off_t off_t;" instead. usr/klibc/ SYSCALLS. def uses off_t for a bunch of syscalls with 32/64-bit alternatives where the kernel uses loff_t for the 64-bit version. Changing these all to loff_t might work, since that's what the kernel was doing anyway.
In the meantime, though, I'm just going to back out this patch to fix booting again.