From: Theodore Ts'o <tytso@mit.edu>
To: linux-ext4@vger.kernel.org
Subject: e2fsprogs update
Date: Tue, 01 Jan 2013 22:24:20 -0500 [thread overview]
Message-ID: <nsxpq1ol123.fsf@closure.thunk.org> (raw)
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
next reply other threads:[~2013-01-02 3:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-02 3:24 Theodore Ts'o [this message]
2013-01-02 15:27 ` e2fsprogs update Theodore Ts'o
2013-01-02 15:54 ` Eric Sandeen
2013-01-02 16:53 ` Theodore Ts'o
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=nsxpq1ol123.fsf@closure.thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.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;
as well as URLs for NNTP newsgroup(s).