Page 1 of 2
(done) Salix 13.1 filesystem
Posted: 16. May 2010, 18:55
by damNageHack
dmesg wrote:EXT3-fs (sda1): error: couldn't mount because of unsupported optional features (240)
EXT2-fs (sda1): error: couldn't mount because of unsupported optional features (240)
EXT4-fs (sda1): mounted filesystem with ordered data mode
Maybe this can be optimized?
Re: Salix 13.1 filesystem
Posted: 16. May 2010, 19:21
by Shador
You could try adding "rootfstype=ext4" as kernel parameter.
Re: Salix 13.1 filesystem
Posted: 16. May 2010, 19:50
by damNageHack
Shador wrote:You could try adding "rootfstype=ext4" as kernel parameter.
Yes, works. Great!
I think it should be added then to standard lilo.conf of Salix 13.1 due to I got the three lines from a fresh installed one. At least if auto-installation was chosen.
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/sda1
label = Linux
read-only
addappend = "rootfstype=ext4"
# Linux bootable partition config ends
Re: Salix 13.1 filesystem
Posted: 17. May 2010, 08:38
by JRD
Hum sounds weird that the kernel needs this parameter...
Anyway, why not on damNageHack's proposition.
Re: Salix 13.1 filesystem
Posted: 19. May 2010, 18:49
by thenktor
The messages don't hurt...

Re: Salix 13.1 filesystem
Posted: 19. May 2010, 19:40
by Shador
+1
Changes needed to support this are in no relation to those messages. In fact, it would only be additional complexity bound to cause real problems at some point.
If somebody thinks he really needs to get rid of those messages, he can add the parameter himself by his own responsibility.
Re: Salix 13.1 filesystem
Posted: 19. May 2010, 19:56
by damNageHack
thenktor wrote:The messages don't hurt...

Shador wrote:+1
Changes needed to support this are in no relation to those messages. In fact, it would only be additional complexity bound to cause real problems at some point.
If somebody thinks he really needs to get rid of those messages, he can add the parameter himself by his own responsibility.
Therefore, I posted in "Suggestions" ...
A newbie may wonder about the three lines when done automatic installation.
Re: Salix 13.1 filesystem
Posted: 19. May 2010, 20:36
by Shador
damNageHack wrote:Therefore, I posted in "Suggestions" ...
Yes, and it was considered, but is unlikely to become implemented as we told you. I guess other distros also would have that "problem" with ext4 (and without initrd). Initrd might change some things.
damNageHack wrote:A newbie may wonder about the three lines when done automatic installation.
So what? He would be told that it's harmless.
Re: Salix 13.1 filesystem
Posted: 19. May 2010, 21:40
by thenktor
damNageHack wrote:A newbie may wonder about the three lines when done automatic installation.
A newbie won't think about anything unless something really does not work because he won't check dmesg messages

Re: (done) Salix 13.1 filesystem
Posted: 6. Aug 2010, 22:47
by lmello
Aren't those messages gone when you make an initrd and boot the generic kernel instead?