From: Eric Sandeen <sandeen@redhat.com>
To: "Pocas, Jamie" <Jamie.Pocas@emc.com>, "Theodore Ts'o" <tytso@mit.edu>
Cc: "linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: resize2fs stuck in ext4_group_extend with 100% CPU Utilization With Small Volumes
Date: Tue, 22 Sep 2015 18:41:16 -0500 [thread overview]
Message-ID: <5601E71C.4080705@redhat.com> (raw)
In-Reply-To: <06724CF51D6BC94E9BEE7A8A8CB82A6740FE22BCDF@MX01A.corp.emc.com>
On 9/22/15 4:26 PM, Pocas, Jamie wrote:
> Hi Theodore,
>
> I am not sure if you had a chance to see my reply to Eric yet. I can
> see you are using the same general approach that Eric was using. The
> key difference from what I am doing again seems to be that I am
> resizing the underlying disk *while the filesystem is mounted*.
Do you see the same problem if you resize a physical disk, not
just with loopback? Sounds like it...
In theory it should be reproducible w/ lvm too, then, I think,
unless there's some issue specific to your block device similar to
what's happening on the loop device.
> Instead you both are using truncate to grow the disk while the
> filesystem is not currently mounted, and then mounting it.
Always worth communicating a testcase in the first email, if you
have one, so we don't have to guess. ;)
thanks,
-Eric
next prev parent reply other threads:[~2015-09-22 23:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-22 19:12 resize2fs stuck in ext4_group_extend with 100% CPU Utilization With Small Volumes Pocas, Jamie
2015-09-22 19:33 ` Eric Sandeen
2015-09-22 20:28 ` Pocas, Jamie
2015-09-22 23:02 ` Theodore Ts'o
2015-09-23 4:20 ` Pocas, Jamie
2015-09-23 15:14 ` Theodore Ts'o
2015-09-23 16:04 ` Pocas, Jamie
2015-09-23 16:59 ` Theodore Ts'o
2015-09-23 18:20 ` Pocas, Jamie
2015-09-22 20:20 ` Theodore Ts'o
2015-09-22 21:26 ` Pocas, Jamie
2015-09-22 23:41 ` Eric Sandeen [this message]
2015-09-23 3:40 ` Pocas, Jamie
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=5601E71C.4080705@redhat.com \
--to=sandeen@redhat.com \
--cc=Jamie.Pocas@emc.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.