All of lore.kernel.org
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: Nick Warne <nick@ukfsn.org>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [QUESTION] root ext4 strange couldn't mount/can mount report
Date: Tue, 27 Jan 2009 10:37:06 -0500	[thread overview]
Message-ID: <20090127153706.GD11843@mit.edu> (raw)
In-Reply-To: <20090127143714.2389b5c2@sauron.linicks.net>

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

  reply	other threads:[~2009-01-27 15:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-27 13:42 [QUESTION] root ext4 strange couldn't mount/can mount report Nick Warne
2009-01-27 14:14 ` Theodore Tso
2009-01-27 14:37   ` Nick Warne
2009-01-27 15:37     ` Theodore Tso [this message]
2009-01-27 15:44       ` Nick Warne

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=20090127153706.GD11843@mit.edu \
    --to=tytso@mit.edu \
    --cc=linux-ext4@vger.kernel.org \
    --cc=nick@ukfsn.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.