From: Ted Ts'o <tytso@mit.edu>
To: Sander Eikelenboom <linux@eikelenboom.it>
Cc: Ext4 Developers List <linux-ext4@vger.kernel.org>,
stable@kernel.org, Kees Cook <keescook@chromium.org>
Subject: Re: [PATCH] ext4: fix the free blocks calculation for ext3 file systems w/ uninit_bg
Date: Thu, 7 Jun 2012 10:10:51 -0400 [thread overview]
Message-ID: <20120607141051.GB2864@thunk.org> (raw)
In-Reply-To: <1511035441.20120607160116@eikelenboom.it>
On Thu, Jun 07, 2012 at 04:01:16PM +0200, Sander Eikelenboom wrote:
>
> BTW: Is there any (real) advantage to recreate the FS using the ext4's flex_bg instead of converting the ext3 to ext4 and using ext3 uninit_bg ?
>
It speeds up e2fsck times, and it allows for more contiguous free
space in the file system. So yes, there is an advantage to using a
native ext4 file system --- but of course that's a pain in the tuckus
for people with large RAID arrays. Which also explains why we were
mainly seeing this bug reported with people using large RAID devices;
those are the people who are most likely to want to do an
upgrade-in-place, because it's too painful to recreate and then copy
the data. Which is fine; one of the major features of ext4 is to be
able to support upgrades-in-place from ext3.
Unfortunately, while I had native (unconverted) ext3 file systems in
my test matrix, I didn't have converted ext3 file system formats in my
regular regression test suite script. That is going to be fixed
shortly....
- Ted
next prev parent reply other threads:[~2012-06-07 14:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-07 13:52 [PATCH] ext4: fix the free blocks calculation for ext3 file systems w/ uninit_bg Theodore Ts'o
2012-06-07 14:01 ` Sander Eikelenboom
2012-06-07 14:10 ` Ted Ts'o [this message]
2012-06-07 14:39 ` Sander Eikelenboom
2012-06-07 17:12 ` Kees Cook
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=20120607141051.GB2864@thunk.org \
--to=tytso@mit.edu \
--cc=keescook@chromium.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux@eikelenboom.it \
--cc=stable@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