linux-ext4 - Re: [QUESTION] root ext4 strange couldn't mount/can mount report

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090127153706.GD11843@mit.edu>
Date:	Tue, 27 Jan 2009 10:37:06 -0500
From:	Theodore Tso <tytso@....edu>
To:	Nick Warne <nick@...sn.org>
Cc:	linux-ext4@...r.kernel.org
Subject: Re: [QUESTION] root ext4 strange couldn't mount/can mount report

On Tue, Jan 27, 2009 at 02:37:14PM +0000, Nick Warne wrote:
> 
> 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? 

The only thing which might not work is automatic type detection with
mount.  That is, if you specify:

	mount /dev/hda1 /boot

without specifying a filesystem type, /bin/mount will probably do an
automatic type detection, detect that the filesystem is an ext3
filesystem, and attempt to mount it as ext3, and not know to try it
with ext4.  Libraries such as blkid and fsid could be made smart
enough to do the right thing, but they don't at the moment.

But if you type "mout -t ext4 /dev/sda1 /boot", you can mount an ext3
filesystem using the ext4 filesystem driver, and with 2.6.29 and up,
you'll be able to mount ext2 filesystems using the ext4 filesystem
code.  (You'll also be able to create extent-based filesystems without
a journal, which is why Google contributed the support for this.)

       	     	       	      	       - Ted
--
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