| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Tue, 27 Jan 2009 14:37:14 +0000 From: Nick Warne <nick@...sn.org> To: Theodore Tso <tytso@....edu> Cc: linux-ext4@...r.kernel.org Subject: Re: [QUESTION] root ext4 strange couldn't mount/can mount report On Tue, 27 Jan 2009 09:14:26 -0500 Theodore Tso <tytso@....edu> wrote: > On Tue, Jan 27, 2009 at 01:42:31PM +0000, Nick Warne wrote: > > > > Jan 27 12:54:57 sauron kernel: EXT3-fs: sda2: couldn't mount > > because of unsupported optional features (40). Jan 27 12:54:57 > > sauron kernel: VFS: Mounted root (ext4 filesystem) readonly. > > > > i.e. root / -> /dev/sda2 couldn't mount, but it does mount, and > > system boots normally and functions fine. > > That's normal; what happens is that the kernel tries to mount it as > ext3 first, which takes a pass since it can't support certain > filesystems features, and then ext4 mounts it. The ext4 filesystem > code will happily mount an ext3 filesystem, so that's why the kernel > tries ext3 first. Hi Ted, I see. I currently build ext3 in the kernel (as well as ext4), as I keep /boot partition ext3 for bootloader lilo. So I can remove ext3 now, and lilo and kernel ext4 will happily read and use /boot partition as ext3 OK? Nick -- Free Software Foundation Associate Member 5508 http://linicks.net/ -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists