From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Kazuya Mio <k-mio@sx.jp.nec.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: double free of blocks occurred during online defrag
Date: Wed, 25 Feb 2009 16:14:46 +0530 [thread overview]
Message-ID: <20090225104446.GA25714@skywalker> (raw)
In-Reply-To: <49A4E7B8.2040804@sx.jp.nec.com>
On Wed, Feb 25, 2009 at 03:39:52PM +0900, Kazuya Mio wrote:
> Hi Aneesh,
>
> When I remove the file that is running online defrag, the following error occurs
> after closing the file descriptor:
>
> Jan 22 17:06:52 G3-OPC-SVR2 kernel: EXT4-fs error (device hda8):
> ext4_mb_release_inode_pa: free 2048, pa_free 1562
> Jan 22 17:06:52 G3-OPC-SVR2 kernel: EXT4-fs error (device hda8): mb_free_blocks:
> double-free of inode 0's block 802817(bit 0 in group 98)
> Jan 22 17:06:52 G3-OPC-SVR2 kernel: EXT4-fs error (device hda8): mb_free_blocks:
> double-free of inode 0's block 802818(bit 1 in group 98)
> Jan 22 17:06:52 G3-OPC-SVR2 kernel: EXT4-fs error (device hda8): mb_free_blocks:
> double-free of inode 0's block 802819(bit 2 in group 98)
> Jan 22 17:06:52 G3-OPC-SVR2 kernel: EXT4-fs error (device hda8): mb_free_blocks:
> double-free of inode 0's block 802820(bit 3 in group 98)
> Jan 22 17:06:52 G3-OPC-SVR2 kernel: EXT4-fs error (device hda8): mb_free_blocks:
> double-free of inode 0's block 802821(bit 4 in group 98)
> Jan 22 17:06:52 G3-OPC-SVR2 kernel: EXT4-fs error (device hda8): mb_free_blocks:
> double-free of inode 0's block 802822(bit 5 in group 98)
>
> So, online defrag calls ext4_discard_preallocations() at the end of
> ext4_defrag() to avoid double-free error.
> However, above error hasn't occurred since applying your patch posted on Nov
> 6th, 2008 because this error is caused by the same reason of your report.
> http://marc.info/?l=linux-ext4&m=122599787406193&w=4
>
> What is the status of this patch?
We dropped the patch because I found that the double free in my case was
not exactly due the explanation given in the patch above.
I asked to drop the patch in
http://article.gmane.org/gmane.comp.file-systems.ext4/10199
I also found that the patch is not completely correct. The meta-data
blocks which are added to the free_list are not allocated from any
prealloc space.
So what you are seeing may be a different problem which the patch is
hiding from happening. I guess you will have to look more closely at why the
double-free is happening in your case.
-aneesh
next prev parent reply other threads:[~2009-02-25 10:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-25 6:39 double free of blocks occurred during online defrag Kazuya Mio
2009-02-25 10:44 ` Aneesh Kumar K.V [this message]
2009-02-25 10:59 ` Aneesh Kumar K.V
2009-02-26 9:49 ` Aneesh Kumar K.V
2009-02-26 22:38 ` Mike Snitzer
2009-03-02 8:30 ` Kazuya Mio
2009-03-06 8:18 ` 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=20090225104446.GA25714@skywalker \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=k-mio@sx.jp.nec.com \
--cc=linux-ext4@vger.kernel.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 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.