From: Eric Sandeen <sandeen@redhat.com>
To: "Theodore Ts'o" <tytso@mit.edu>,
"Darrick J. Wong" <darrick.wong@oracle.com>
Cc: Chris Hunter <chris.hunter@yale.edu>, linux-ext4@vger.kernel.org
Subject: Re: errors following ext3 to ext4 conversion
Date: Thu, 27 Aug 2015 16:34:05 -0500 [thread overview]
Message-ID: <55DF824D.7040302@redhat.com> (raw)
In-Reply-To: <20150827185845.GB3357@thunk.org>
On 8/27/15 1:58 PM, Theodore Ts'o wrote:
> I suspect that would fill Eric's heart with horror, but the ability to
> migrate the root file system from ext2 to ext3 while it was mounted
> (i.e., just run "tune2fs -O has_journal /dev/rootfs" and reboot) was
> something Stephen Tweedie added, so at least at one point Red Hat was
> more adventurous about what it would support in terms of file system
> upgrades without using mkfs. :-)
>
> - Ted
Oh, it doesn't fill me with *that* much horror. ;)
TBH, my big problem with the ext3->ext4 "migration" is that you wind
up with a mongrel filesystem which mkfs.ext4 would never create,
populated with files of varying runtime limitations and capabilities,
depending on whether they were created before or after the "migration."
Adding a journal and rebooting at least gets you to a pretty standard,
predictable, and tested result. ;)
-Eric
next prev parent reply other threads:[~2015-08-27 21:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-27 0:53 errors following ext3 to ext4 conversion Chris Hunter
2015-08-27 3:39 ` Theodore Ts'o
2015-08-27 3:43 ` Eric Sandeen
2015-08-27 4:15 ` Darrick J. Wong
2015-08-27 18:58 ` Theodore Ts'o
2015-08-27 19:28 ` Chris Hunter
2015-08-27 22:46 ` Theodore Ts'o
2015-08-28 16:23 ` Chris Hunter
2015-08-28 18:32 ` Theodore Ts'o
2015-08-27 21:34 ` Eric Sandeen [this message]
2015-08-28 16:09 ` 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=55DF824D.7040302@redhat.com \
--to=sandeen@redhat.com \
--cc=chris.hunter@yale.edu \
--cc=darrick.wong@oracle.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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.