public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@dilger.ca>
To: linux_ext4@proinbox.com
Cc: linux-ext4@vger.kernel.org
Subject: Re: convert from ext3 versus fresh format
Date: Sun, 28 Nov 2010 22:51:22 -0700	[thread overview]
Message-ID: <F4A59BB4-367A-4F65-AC38-299ADCAF19FB@dilger.ca> (raw)
In-Reply-To: <1290978963.16103.1407558601@webmail.messagingengine.com>

On 2010-11-28, at 14:16, linux_ext4@proinbox.com wrote:
> I have a production system installed on an SSD, whose installer formats
> the target drive as ext3 automatically. I've since learned that ext4 is
> more suited for use on SSDs and am considering an upgrade to ext4.
> 
> I see the procedure on how to convert from ext3 to ext4 on the wiki, and
> before I proceed would like to know whether there's an advantage to
> formatting as ext4 from the start as opposed to converting after an ext3
> format.

It is possible to use the ext4 filesystem code on ext3-formatted filesystems without any conversion being done.  Enabling extents will improve performance, and uninit_bg will improve e2fsck performance.

You wouldn't be able to take advantage of flex_bg without reformatting (or some significant surgery to resize2fs).

If the inodes are "large" (256 bytes) then mounting the filesystem with ext4 will allow the inodes to use nanosecond timestamps.

> In the case that there is a difference, what exactly is sacrificed in
> choosing one over the other?

Reformatting and reinstalling and/or restoring from backup into an ext4-formatted filesystem will allow using a few of the features lay out the files with extents, and reduce the metadata overhead.  There will be some performance benefits, but I don't think it will necessarily be dramatic.

Cheers, Andreas






  reply	other threads:[~2010-11-29  5:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-28 21:16 convert from ext3 versus fresh format linux_ext4
2010-11-29  5:51 ` Andreas Dilger [this message]
2010-11-29  5:52 ` Michael Rubin
2010-11-29 17:29 ` Greg Freemyer

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=F4A59BB4-367A-4F65-AC38-299ADCAF19FB@dilger.ca \
    --to=adilger@dilger.ca \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux_ext4@proinbox.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox