From: Stroller <stroller@stellar.eclipse.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] ext4/ext3 for /boot?
Date: Mon, 7 Nov 2011 20:42:53 +0000 [thread overview]
Message-ID: <A41D6CA8-A730-45ED-A965-463DBE2B077A@stellar.eclipse.co.uk> (raw)
In-Reply-To: <CA+czFiCvLcCUGNHTn-MS0Gxf1rsJ7rKx9AdRyaJ4Vs0rDRcpuw@mail.gmail.com>
On 7 November 2011, at 19:32, Michael Mol wrote:
> On Mon, Nov 7, 2011 at 2:26 PM, Alan McKinnon <alan.mckinnon@gmail.com> wrote:
>> ext2/3/4 are all backwards compatible. ext4 does have a certain feature
>> (I forget what) that once used breaks this compatibility but you are
>> highly, highly unlikely to ever do that on /boot.
>
> "Extents," I believe. But I don't know exactly what that means, or
> when it comes into play.
It means, as a huge simplification, that ext4 can allocate a file to blocks 1234 - 1256, instead of having to separately allocate blocks 1234, 1235, 1236, 1237, 1238, 1239, 1240, and so on (as ext3 would have had to do).
This fixes ext3's "slow deletes" problem, because only a single entry in the allocation table needs to be removed, instead of many. If you delete a big file (say a 9gig DVD or 40gig blu-ray .iso image file) it's at least an order of magnitude slower on ext3 than it is on ext4.
As I said, this is a huge simplification, and I'm sure there are folks who would take pleasure in explaining how wrong it is, but it's a good enough explanation for a couple of sentences that you can easily grasp. For more details the "Features - Extents" section of ext4's wikipedia page [1] and this other article [2] (these are top hits on Google for "ext4 extents") look pretty good.
Stroller.
[1] http://en.wikipedia.org/wiki/Ext4#Features
[2] http://computer-forensics.sans.org/blog/2011/03/28/digital-forensics-understanding-ext4-part-3-extent-trees
next prev parent reply other threads:[~2011-11-07 20:44 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-07 18:29 [gentoo-user] ext4/ext3 for /boot? Jarry
2011-11-07 18:37 ` Stéphane Guedon
2011-11-07 19:26 ` Alan McKinnon
2011-11-07 19:32 ` Michael Mol
2011-11-07 20:41 ` [gentoo-user] " Nikos Chantziaras
2011-11-07 20:42 ` Stroller [this message]
2011-11-07 21:14 ` [gentoo-user] " Michael Mol
2011-11-08 8:37 ` Alan Mackenzie
2011-11-08 9:49 ` Dale
2011-11-08 11:15 ` Pandu Poluan
2011-11-08 12:35 ` Neil Bothwick
2011-11-08 13:11 ` Pandu Poluan
2011-11-08 14:14 ` Dale
2011-11-08 21:59 ` Sebastian Beßler
2011-11-08 22:07 ` Paul Hartman
2011-11-09 2:44 ` Pandu Poluan
2011-11-09 9:39 ` Neil Bothwick
2011-11-09 11:39 ` Pandu Poluan
2011-11-09 3:03 ` bill.longman
2011-11-09 4:16 ` Pandu Poluan
2011-11-09 4:18 ` Pandu Poluan
2011-11-09 5:22 ` bill.longman
2011-11-09 6:42 ` Pandu Poluan
2011-11-09 1:36 ` J.Marcos Sitorus
2011-11-08 15:52 ` Stroller
2011-11-08 16:00 ` Neil Bothwick
2011-11-08 18:59 ` David Guillermo
2011-11-09 18:18 ` Alan McKinnon
2011-11-07 19:38 ` Alex Schuster
2011-11-08 0:41 ` pk
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=A41D6CA8-A730-45ED-A965-463DBE2B077A@stellar.eclipse.co.uk \
--to=stroller@stellar.eclipse.co.uk \
--cc=gentoo-user@lists.gentoo.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