On Mon, Jan 20, 2014 at 02:52:43PM -0700, Andreas Dilger wrote:
> On Jan 19, 2014, at 10:54 PM, Theodore Ts'o <tytso@xxxxxxx> wrote:
> > If there are hundreds of thousands of blocks which are in use before
> > the first free block, it is much, MUCH faster to use
> > ext2fs_find_first_zero_block_bitmap2() instead of searching the
> > allocation bitmap bit by bit.
>
> Excellent. The libext2fs block allocator has typically been unusable
> for filesystems with allocated blocks, so it is good to see this.
Yes, all of these patches should fix the following e-mail message
question which you raised a while back:
------------
Date: Fri, 28 May 2010 13:25:45 -0600
From: Andreas Dilger <andreas.dilger@xxxxxxxxxx>
To: "linux-ext4@xxxxxxxxxxxxxxx development" <linux-ext4@xxxxxxxxxxxxxxx>
Cc: Zhiqi Tao <zhiqi.tao@xxxxxxxxxx>
Subject: Huge flex_bg count kills mke2fs
X-Mailer: Apple Mail (2.1078)
We're trying to put all of the static ext4 metadata at the beginning
of the disk to see whether this gives us a performance improvement
(avoid seeking during e2fsck, avoid free space fragmentation). This
is on a filesystem somewhat smaller than 16TB, and the flex_bg count
131072 would seem large enough to put all of groups into a single flex
group.
However, running the below command spins forever, apparently trying to
allocate the static metadata:
mke2fs -j -b 4096 -G 131072 -J size=1024 -i 65536 \
-O flex_bg,uninit_bg,extents -I 256 -F /dev/vgost0/lvost0 4294965248
...
-----------
(I found it a while today when I was doing some mail searching.)
> This could be further improved by skipping full groups entirely, but
> that doesn't detract from the benefits of this patch.
Actually, given that we're using a red-black tree for the block
bitmaps these days, it's actually much more efficient than checking
the block counts to see which block groups might be free. If the
first 4,000 block groups have been fully allocated, there will be a
single entry node in the red-black tree. :-)
- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
