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] [day] [month] [year] [list]
Date:	Thu, 21 May 2009 01:01:46 -0400
From:	Andreas Dilger <adilger@....com>
To:	Matt LaPlante <cybrmatt@...il.com>
Cc:	Eric Sandeen <sandeen@...hat.com>, linux-ext4@...r.kernel.org
Subject: Re: Mounting Ext3 with Ext4

On May 21, 2009  00:37 -0400, Matt LaPlante wrote:
> It looks likes the magic touch was to add rootfstype=ext4 to the
> kernel command line.  Prior to this the ext4 only kernel wasn't
> finding the disk, but with it attached it now appears to boot
> successfully.  Maybe worth adding a note to the wiki?

This means that your initrd has "ext3" as the root filesystem type
in /etc/fstab or similar.  If the filesystem type is explicitly
given as "ext3" then the ext4 driver will not try to mount it.


I suppose it might be reasonable to have a config option that adds
the "ext3" and "ext2" filesystem types to the ext4 driver for cases
like this where CONFIG_EXT2 and CONFIG_EXT3 (and module equivalents)
are disabled.

Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.

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

Powered by Openwall GNU/*/Linux Powered by OpenVZ