From: Akira Fujita <a-fujita@rs.jp.nec.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: Theodore Tso <tytso@mit.edu>, Li Zefan <lizf@cn.fujitsu.com>,
linux-ext4@vger.kernel.org
Subject: Re: [PATCH]ext4: fix s_dirty_blocks_counter if block allocation failed with nodelalloc
Date: Thu, 04 Dec 2008 17:32:58 +0900 [thread overview]
Message-ID: <493795BA.4010507@rs.jp.nec.com> (raw)
In-Reply-To: <20081204050745.GC10787@skywalker>
Aneesh Kumar K.V wrote:
> On Thu, Dec 04, 2008 at 10:27:25AM +0900, Akira Fujita wrote:
>> Hi Aneesh,
>> Aneesh Kumar K.V wrote:
>>> On Mon, Dec 01, 2008 at 07:21:54PM +0900, Akira Fujita wrote:
>>>> ext4: Fix s_dirty_blocks_counter if block allocation failed with nodelalloc
>>>>
>>>> From: Akira Fujita <a-fujita@rs.jp.nec.com>
>>>>
>>>> If block allocation failed after marking claimed blocks as dirty blocks
>>>> with nodelalloc, we have to subtract these blocks from
>>>> s_dirty_blocks_counter in error handling.
>>>> Otherwise s_dirty_blocks_counter goes wrong so that
>>>> filesystem's free blocks decreases incorrectly.
>>> Why did the block allocation fail ? With delayed allocation ENOSPC
>>> should not happen during block allocation. That would mean we did
>>> something wrong in block reservation.
>> My case was *nodelalloc* and FS was almost full.
>> This problem occurs in multiple defrag running in short time.
>> Usually defrag releases temporary inode's blocks with iput,
>> then FS free blocks are recover but contiguous blocks do not recover
>> until next journal commit.
>> so we can not re-use contiguous blocks immediately.
>> There are enough free blocks in FS so that
>> ext4_claim_free_blocks marks claimed blocks as dirty,
>> but ext4_regular_allocator can not find enough blocks,
>> so mb_new_blocks returns ENOSPC without decreasing dirty blocks.
>>
> ok how about doing the check once in ext4_mb_new_blocks.
It works fine. Thank you.
Tested-by: Akira Fujita <a-fujita@rs.jp.nec.com>
> diff --git a/fs/ext4/mballoc.c b/fs/ext4/mballoc.c
> index bacc2f4..22d31c3 100644
> --- a/fs/ext4/mballoc.c
> +++ b/fs/ext4/mballoc.c
> @@ -4550,7 +4550,7 @@ ext4_fsblk_t ext4_mb_new_blocks(handle_t *handle,
> }
> if (ar->len == 0) {
> *errp = -EDQUOT;
> - return 0;
> + goto out3;
> }
> inquota = ar->len;
>
> @@ -4623,6 +4623,13 @@ ext4_fsblk_t ext4_mb_new_blocks(handle_t *handle,
> out1:
> if (ar->len < inquota)
> DQUOT_FREE_BLOCK(ar->inode, inquota - ar->len);
> +out3:
> + if (!ar->len) {
> + if (!EXT4_I(ar->inode)->i_delalloc_reserved_flag)
> + /* release all the reserved blocks if non delalloc */
> + percpu_counter_sub(&sbi->s_dirtyblocks_counter,
> + reserv_blks);
> + }
>
> return block;
> }
next prev parent reply other threads:[~2008-12-04 8:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-01 10:21 [PATCH]ext4: fix s_dirty_blocks_counter if block allocation failed with nodelalloc Akira Fujita
2008-12-01 10:36 ` Aneesh Kumar K.V
2008-12-04 1:27 ` Akira Fujita
2008-12-04 5:07 ` Aneesh Kumar K.V
2008-12-04 8:32 ` Akira Fujita [this message]
2008-12-04 8:38 ` Li Zefan
-- strict thread matches above, loose matches on Subject: below --
2008-12-04 14:04 [PATCH] ext4: Fix " Aneesh Kumar K.V
2008-12-04 18:19 ` Mingming Cao
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=493795BA.4010507@rs.jp.nec.com \
--to=a-fujita@rs.jp.nec.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=lizf@cn.fujitsu.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).