All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: Matt LaPlante <cybrmatt@gmail.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Mounting Ext3 with Ext4
Date: Wed, 20 May 2009 20:17:32 -0500	[thread overview]
Message-ID: <4A14ABAC.7040901@redhat.com> (raw)
In-Reply-To: <baab8ccb0905201624j56767f59mff537ab8767ffc8d@mail.gmail.com>

Matt LaPlante wrote:
> According to the Ext4 howto
> (http://ext4.wiki.kernel.org/index.php/Ext4_Howto#Converting_an_ext3_filesystem_to_ext4),
> "It is possible to mount both ext3 (and ext2, in kernels 2.6.28 and
> later) filesystems directly using the ext4 filesystem driver."  So
> this means, if I'm reading it correctly, that a kernel built with ext4
> support should be able to mount and manage ext[234] filesystems.  Is
> that correct?  If so, are there any limitations on this support?
> 
> I'm running Ubuntu Jaunty with some custom-built 2.6.29.4 kernels and
> grub2.  I seem to have no problem booting from ext4 disks, so the ext4
> support is definitely there and functioning.  I had hoped the ext3
> support meant I could build the kernel with ext4 only and carry on as
> usual with my ext3 partitions.  Unfortunately doing so causes the ext3
> partitions to fail to boot.  So...
> 
> booting ext3 with ext3 in the kernel=fine
> booting ext4 with ext4 in the kernel=fine
> booting ext3 with ext4 (only) in the kernel=not fine
> 
> Is this a problem or was it never intended to work?

It should work...

It'd be more helpful if you could include details on exactly how it
failed, but if Ubuntu builds ext4 as a module, perhaps the initrd
creation sees root as ext3 and doesn't bother to put ext4 in the initrd?

-Eric

  reply	other threads:[~2009-05-21  1:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-20 23:24 Mounting Ext3 with Ext4 Matt LaPlante
2009-05-21  1:17 ` Eric Sandeen [this message]
2009-05-21  1:28   ` Matt LaPlante
2009-05-21  4:37     ` Matt LaPlante
2009-05-21  4:53       ` Eric Sandeen
2009-05-21  5:01       ` Andreas Dilger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A14ABAC.7040901@redhat.com \
    --to=sandeen@redhat.com \
    --cc=cybrmatt@gmail.com \
    --cc=linux-ext4@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.