From: Chanho Park <chanho61.park@samsung.com>
To: tytso@mit.edu
Cc: darrick.wong@oracle.com, linux-ext4@vger.kernel.org
Subject: [e2fsprogs] resizing to minimum was failed since 45a78b
Date: Wed, 29 Apr 2015 17:33:20 +0900 [thread overview]
Message-ID: <01cb01d08257$26157350$724059f0$@samsung.com> (raw)
Hi,
When I tried to resize a loop ext4 image to minimum, I couldn't get correct
result.
Please see below test and results:
1. e2fsprogs 1.43-WIP version:
mke2fs -F -t ext4 foo.img 512M
mount foo.img mnt1
dd if=/dev/zero of=mnt1/test bs=1M count=350
df | grep mnt1
/dev/loop0 499656 358796 104164 78% /mnt1
umount mnt1
e2fsck -f foo.img
resize2fs -M foo.img
resize2fs 1.43-WIP (29-Mar-2015)
Resizing the filesystem on foo.img to 129175 (4k) blocks.
The filesystem on foo.img is now 129175 (4k) blocks long.
ls -al foo.img
-rw-r--r-- 1 root root 529100800 Apr 29 08:00 foo.img
2. e2fsprogs 1.42.9 version:
mke2fs -F -t ext4 bar.img 512M
mount bar.img mnt2
dd if=/dev/zero of=mnt2/test bs=1M count=350
umount mnt2
e2fsck -f bar.img
resize2fs -M bar.img
resize2fs 1.42.9 (28-Dec-2013)
Resizing the filesystem on bar.img to 103592 (4k) blocks.
The filesystem on bar.img is now 103592 blocks long.
ls -al bar.img
-rw-r--r-- 1 root root 424312832 Apr 29 08:04 bar.img
1.43-WIP version: 529100800 -> 529100800
1.42.9 version: 529100800 -> 424312832
Furthermore, the resizing to minimum was failed if the loop image was filled
over 84%.
I found it was changed since (45a78b8 resize2fs: refine minimum required
blocks for flex_bg file systems)
Is it correct or something's wrong?
Best Regards,
Chanho Park
next reply other threads:[~2015-04-29 8:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-29 8:33 Chanho Park [this message]
2015-04-29 14:29 ` [e2fsprogs] resizing to minimum was failed since 45a78b Theodore Ts'o
2015-04-30 10:12 ` Chanho Park
2015-04-30 15:13 ` Theodore Ts'o
2015-04-30 17:05 ` Darrick J. Wong
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='01cb01d08257$26157350$724059f0$@samsung.com' \
--to=chanho61.park@samsung.com \
--cc=darrick.wong@oracle.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.