From: Greg Freemyer <greg.freemyer@gmail.com>
To: Kazuya Mio <k-mio@sx.jp.nec.com>
Cc: Tomasz Chmielewski <mangoo@wpkg.org>, linux-ext4@vger.kernel.org
Subject: Re: [PATCH 00/11 RESEND] e4defrag: fragmentation score rework and cleanups
Date: Fri, 17 Jun 2011 09:08:19 -0400 [thread overview]
Message-ID: <BANLkTimFCQNt=Bptn-rhPeTbYRgfGdQLxQ@mail.gmail.com> (raw)
In-Reply-To: <4DFAE285.9010503@sx.jp.nec.com>
On Fri, Jun 17, 2011 at 1:13 AM, Kazuya Mio <k-mio@sx.jp.nec.com> wrote:
> 2011/06/16 17:18, Tomasz Chmielewski wrote:
>>
>> I noticed that when using e4defrag on such a file-based image, while the
>> guest is running (i.e. the file is in use), all IO from that guest to
>> the disk (disk is this file) is "frozen".
>>
>> In other words, as soon as we run e4defrag, any guest writes to that
>> file will only complete if e4defrag finishes. As the images can be quite
>> big, it can mean guest IO can be frozen even for hours.
>>
>>
>> Is it a known/intended limitation (at least, it behaved like this when I
>> tried e4defrag a few months ago)?
>
> Thank you for the feedback. I will try to reproduce this problem later.
>
> Regards,
> Kazuya Mio
Kazuya,
When trying to come up with a better plan for handling large files,
you may want to review this msg and Akira's response from last spring:
http://www.kerneltrap.com/mailarchive/linux-ext4/2010/3/30/6899823
Greg
next prev parent reply other threads:[~2011-06-17 13:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-15 20:31 [PATCH 00/11 RESEND] e4defrag: fragmentation score rework and cleanups Tomasz Chmielewski
2011-06-16 5:10 ` Kazuya Mio
2011-06-16 8:18 ` Tomasz Chmielewski
2011-06-17 5:13 ` Kazuya Mio
2011-06-17 13:08 ` Greg Freemyer [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-06-15 6:33 Kazuya Mio
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='BANLkTimFCQNt=Bptn-rhPeTbYRgfGdQLxQ@mail.gmail.com' \
--to=greg.freemyer@gmail.com \
--cc=k-mio@sx.jp.nec.com \
--cc=linux-ext4@vger.kernel.org \
--cc=mangoo@wpkg.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).