[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <nsxpq1ol123.fsf@closure.thunk.org>
Date: Tue, 01 Jan 2013 22:24:20 -0500
From: Theodore Ts'o <tytso@....edu>
To: linux-ext4@...r.kernel.org
Subject: e2fsprogs update
I've just pushed out large number of updates to e2fsprogs's git
repository. The maint branch is close to what I hope to release as
1.42.7. It has the flex_bg resize2fs fixes, and is gcc -Wall clean.
Please test it out, and let me know if you see any issues before we do a
release.
One known issue. There still seems to be some resize2fs problems when
the 64-bit feature is set when doing off-line (unmounted) resizing:
touch /mnt/testfs
truncate -s 8T /mnt/testfs
mke2fs -t ext4 -O 64bit /mnt/testfs
e2fsck -fy /mnt/testfs
truncate -s 20T /mnt/testfs
resize2fs -p /mnt/testfs
e2fsck -fy /mnt/testfs
#
# Pass 5 errors found:
#
# Free blocks count wrong (1031374305, counted=5326341601).
# Fix<y>? yes
truncate -s 21T /mnt/testfs
resize2fs -p /mnt/testfs
e2fsck -fy /mnt/testfs
#
# Pass 5 errors found:
#
# Block bitmap differences: +(1073774592--1073807359)
# Fix<y>? yes
# Free blocks count wrong for group #32769 (32768, counted=0).
# Fix<y>? yes
# Free blocks count wrong (1297725793, counted=5592660321).
# Fix<y>? yes
Apparently somehow the blocks associated with the journal inode got
released as part of the resize2fs. I'm not sure what's going on, but
this is clearly something we'll want to fix up before we release 1.42.7.
Still, it's much less serious set of problems than we had before.
- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists