From: Greg Freemyer <greg.freemyer@gmail.com>
To: Peng Tao <bergwolf@gmail.com>
Cc: SandeepKsinha <sandeepksinha@gmail.com>,
ext4 <linux-ext4@vger.kernel.org>, Theodore Tso <tytso@mit.edu>
Subject: Re: kernel BUG at fs/ext4/move_extent.c:1317!
Date: Mon, 21 Sep 2009 15:06:15 -0400 [thread overview]
Message-ID: <87f94c370909211206q6a265d13r7ea868900dd013ee@mail.gmail.com> (raw)
In-Reply-To: <6149e97b0909201822y5f29d091jbc00b740244f39a8@mail.gmail.com>
resend - I inadvertently was not in plain text mode before.
On Sun, Sep 20, 2009 at 9:22 PM, Peng Tao <bergwolf@gmail.com> wrote:
> Hi, Sandeep,
>
> On Sun, Sep 20, 2009 at 9:25 PM, SandeepKsinha <sandeepksinha@gmail.com> wrote:
>> Hi Akira/others,
>>
>> I hit the following assert kernel BUG at fs/ext4/move_extent.c:1317!
>>
>> The file I was playing around with was a simple holey file created like:
>>
>> [/mnt]
>> [18:35:13 sinhas]$ dd if=/dev/zero of=/mnt/ext4image seek=1000 count=5
>> 5+0 records in
>> 5+0 records out
>> 2560 bytes (2.6 kB) copied, 0.000146457 s, 17.5 MB/s
>>
>> I am using v2.6.31. I have seen some patchsets a couple of days from
>> you. Does any of them address any similar problem.?
> Yes. The BUG_ON is unnecessary and is removed in the latest mainline
> kernel. Please refer to commit
> daea696dbac0e33af3cfe304efbfb8d74e0effe6 for details.
<snip>
> --
> Cheers,
> Peng Tao
Ted,
I think the few small ext4_move_ext() / e4defrag related fixes for
sparse files to work should get pushed to stable. I don't know if
this is the only one or if there are others.
Greg
prev parent reply other threads:[~2009-09-21 19:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-20 13:25 kernel BUG at fs/ext4/move_extent.c:1317! SandeepKsinha
2009-09-21 1:22 ` Peng Tao
2009-09-21 19:06 ` Greg Freemyer [this message]
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=87f94c370909211206q6a265d13r7ea868900dd013ee@mail.gmail.com \
--to=greg.freemyer@gmail.com \
--cc=bergwolf@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeepksinha@gmail.com \
--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 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).