public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: linux_ext4@proinbox.com
To: linux-ext4@vger.kernel.org
Subject: convert from ext3 versus fresh format
Date: Sun, 28 Nov 2010 16:16:03 -0500	[thread overview]
Message-ID: <1290978963.16103.1407558601@webmail.messagingengine.com> (raw)

Hi list,

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.

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

Regards,

-C


             reply	other threads:[~2010-11-28 21:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-28 21:16 linux_ext4 [this message]
2010-11-29  5:51 ` convert from ext3 versus fresh format Andreas Dilger
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=1290978963.16103.1407558601@webmail.messagingengine.com \
    --to=linux_ext4@proinbox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox