[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <87f94c370909211206q6a265d13r7ea868900dd013ee@mail.gmail.com>
Date: Mon, 21 Sep 2009 15:06:15 -0400
From: Greg Freemyer <greg.freemyer@...il.com>
To: Peng Tao <bergwolf@...il.com>
Cc: SandeepKsinha <sandeepksinha@...il.com>,
ext4 <linux-ext4@...r.kernel.org>, Theodore Tso <tytso@....edu>
Subject: Re: kernel BUG at fs/ext4/move_extent.c:1317!
resend - I inadvertently was not in plain text mode before.
On Sun, Sep 20, 2009 at 9:22 PM, Peng Tao <bergwolf@...il.com> wrote:
> Hi, Sandeep,
>
> On Sun, Sep 20, 2009 at 9:25 PM, SandeepKsinha <sandeepksinha@...il.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
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists