From: tytso@mit.edu
To: SandeepKsinha <sandeepksinha@gmail.com>
Cc: Greg Freemyer <greg.freemyer@gmail.com>,
Akira Fujita <a-fujita@rs.jp.nec.com>,
ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: Question about ext4 online defrag test case
Date: Sat, 16 Jan 2010 01:29:31 -0500 [thread overview]
Message-ID: <20100116062930.GB25273@thunk.org> (raw)
In-Reply-To: <37d33d831001150541o1b674580u14719e72e3ad8e78@mail.gmail.com>
On Fri, Jan 15, 2010 at 07:11:28PM +0530, SandeepKsinha wrote:
> >> I found your comment about ext4 online defrag on Ubuntu BBS by accident.
> >> https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/321528
> >>
> >> I would like to address this problem so I ran e4defrag on the system
> >> which was under memory pressure. But unfortunately I could not find the bug.
> >> If you have already known how to reproduce this kind of problem,
> >> could you teach me how?
I'm sorry I wasn't clear. I don't know of any specific problem with
the code, but I and some other ext4 developers remain a bit conerned
about the code because of how it is structured, and the fact that
there is so much code and there hasn't been a lot of people spent a
lot of time going through it and cleaning it up. We also don't have
good regression tests for the kernel defrag support code.
This is partially my fault; I haven't had enough time to do more
testing and code clean up on the defrag code. I need to spend more
time doing some testing and code cleanup before I'll be comfortable
telling people that it is as reliable as other parts of ext4 in terms
of not potentially losing their data. Maybe it's just my paranoia....
- Ted
next prev parent reply other threads:[~2010-01-16 6:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-14 10:19 Question about ext4 online defrag test case Akira Fujita
2010-01-14 21:04 ` Greg Freemyer
2010-01-15 13:41 ` SandeepKsinha
2010-01-16 6:29 ` tytso [this message]
2010-01-16 17:28 ` Manish Katiyar
2010-01-19 4:37 ` Akira Fujita
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=20100116062930.GB25273@thunk.org \
--to=tytso@mit.edu \
--cc=a-fujita@rs.jp.nec.com \
--cc=greg.freemyer@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeepksinha@gmail.com \
/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.