LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   Is it a bug of klibc? If so, how can I update it? (http://www.linuxquestions.org/questions/slackware-14/is-it-a-bug-of-klibc-if-so-how-can-i-update-it-842673/)

yangzhichina 11-05-2010 11:23 PM

Is it a bug of klibc? If so, how can I update it?
 
Hi Guys.

I am new to Slackware. Last night, I finished my installation of Slackware, but there is a issue when system's starting-up.

I have 3 partitions for linux. (Other 3 ones for Windows)

/dev/sda8 /boot ext2
/dev/sda9 / ext4
/dev/sda10 /home ext4

These information above is listed in the /etc/fstab, actually they are true, but I get a error message during starting-up of Slackware. I am told as fellow:
"ext3-fs (/dev/sda9): error: Couldn't mount because of unsupported optional feature (240)"
"ext2-fs (/dev/sda9): error: Couldn't mount because of unsupported optional feature (240)"
"ext4-fs (/dev/sda9): Mounted filesystem with ordered data mode."

It is wired. My /dev/sda9 is truly ext4, I formatted it as ext4 by myself on the installation of Slackware. Why the system want to mount it as ext3 firstly, then ext2, eventually ext4?

After a moment on Google, I guess it is a bug of klibc because of checking "https://bugzilla.kernel.org/show_bug.cgi?id=12354". But I am not sure about it.

Could anyone help me fix it? It will be appreciated.

Jeffrey.

yangzhichina 11-05-2010 11:45 PM

Someone in China have fixed it using GRUB loader, but I am using LILO, the default loader on Slackware. What can I do?

The following is his solution:

menuentry "Gentoo GNU/Linux, with Linux 2.6.35.7" --class gentoo --class gnu-linux --class gnu --class os {
insmod ext2
set root='(hd0,3)'
search --no-floppy --fs-uuid --set eaffe5af-76f1-4beb-abd3-5e7994c8d606
echo Loading Linux 2.6.35.7 ...
linux /vmlinuz-2.6.35.7 root=/dev/sda1 ro quiet rootfstype=ext4
}

Please pay your attention on this text of Bold Font.

Could I fix this issue using rootfstype=ext4 on LILO?

willysr 11-06-2010 01:28 AM

try adding this line in /etc/lilo.conf
append "rootfstype=ext4"

and re-run lilo
/sbin/lilo -v

yangzhichina 11-06-2010 11:24 AM

Guys, there is a good news about this question. I've got reply from Patrick, the creator of Slackware. (Of course, I sent a email to him.)

The followings are his reply:

Quote:

On 11/05/2010 11:23 PM, Jeffrey Young wrote:

Hi Patrick

I am new to Slackware. Last night, I finished my installation of Slackware,
but there is a issue when system's starting-up.

I have 3 partitions for linux. (Other 3 ones for Windows)

/dev/sda8 /boot ext2
/dev/sda9 / ext4
/dev/sda10 /home ext4

These information above is listed in the /etc/fstab, actually they are true,
but I get a error message during starting-up of Slackware. I am told as
fellow:
"ext3-fs (/dev/sda9): error: Couldn't mount because of unsupported optional
feature (240)"
"ext2-fs (/dev/sda9): error: Couldn't mount because of unsupported optional
feature (240)"
"ext4-fs (/dev/sda9): Mounted filesystem with ordered data mode."

It is wired. My /dev/sda9 is truly ext4, I formatted it as ext4 by myself on
the installation of Slackware. Why the system want to mount it as ext3
firstly, then ext2, eventually ext4?


I will guess that you are still booting with the "huge" kernel rather than with an initrd and a generic kernel. The kernel has all of those filesystems built into it, and doesn't really know what filesystem type /dev/sda9 is until it starts to examine it. So you see 2 failed mount attempts, and then it works. That's just the order the kernel happens to try.

Anyway, if you switch to an initrd/generic boot, it won't emit those messages. It's not hurting anything, though.


After a moment on Google, I guess it is a bug of klibc because of checking "
https://bugzilla.kernel.org/show_bug.cgi?id=12354". But I am not sure about
it.



Nope, we don't use klibc in Slackware.

Take care,

Pat

yangzhichina 11-07-2010 12:12 AM

Quote:

Originally Posted by willysr (Post 4150856)
try adding this line in /etc/lilo.conf
append "rootfstype=ext4"

and re-run lilo
/sbin/lilo -v

Please forget the "rootfstype=ext4". These error messages don't matter. Nothing will be hurting there.

yangzhichina 11-07-2010 12:18 AM

Quote:

Originally Posted by yangzhichina (Post 4150809)
Someone in China have fixed it using GRUB loader, but I am using LILO, the default loader on Slackware. What can I do?

The following is his solution:

menuentry "Gentoo GNU/Linux, with Linux 2.6.35.7" --class gentoo --class gnu-linux --class gnu --class os {
insmod ext2
set root='(hd0,3)'
search --no-floppy --fs-uuid --set eaffe5af-76f1-4beb-abd3-5e7994c8d606
echo Loading Linux 2.6.35.7 ...
linux /vmlinuz-2.6.35.7 root=/dev/sda1 ro quiet rootfstype=ext4
}

Please pay your attention on this text of Bold Font.

Could I fix this issue using rootfstype=ext4 on LILO?

Forget it. It's not a right way. Please refer to Patrick's reply.


All times are GMT -5. The time now is 02:24 AM.