From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Alex Tomas <bzzz@sun.com>, Andreas Dilger <adilger@sun.com>
Cc: "linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: mballoc and inode prealloc space deletion
Date: Tue, 8 Jan 2008 16:23:41 +0530 [thread overview]
Message-ID: <20080108105341.GA11659@skywalker> (raw)
Hi Alex,
With the latest changes i see both group preallocation and inode
preallocation being used by mballoc. Since the choice is now made with
file size not just the request size. (None of the test were actually
using inode prealloc previously). Now that the test are using inode prealloc i
see the below dump stack on the console. I guess you put in the dump
stack there to find out how often these happen. Do you still want the
dump stack to be there. Or can I remove it. ?
uh-oh! some one just deleted it
Call Trace:
[c0000000e4143970] [c000000000010554] .show_stack+0x6c/0x1a0
(unreliable)
[c0000000e4143a10] [c00000000019db90]
.ext4_mb_discard_inode_preallocations+0x1d4/0x428
[c0000000e4143b20] [c000000000178e8c]
.ext4_discard_reservation+0x30/0xb4
[c0000000e4143bc0] [c00000000017c0b8] .ext4_release_file+0x54/0xbc
[c0000000e4143c50] [c0000000000de4b0] .__fput+0x114/0x214
[c0000000e4143d00] [c0000000000db2d8] .filp_close+0xb0/0xd8
[c0000000e4143d90] [c0000000000dbb20] .sys_close+0xc4/0x128
[c0000000e4143e30] [c00000000000872c] syscall_exit+0x0/0x40
uh-oh! some one just deleted it
Call Trace:
[c0000000ede97970] [c000000000010554] .show_stack+0x6c/0x1a0
(unreliable)
[c0000000ede97a10] [c00000000019db90]
.ext4_mb_discard_inode_preallocations+0x1d4/0x428
[c0000000ede97b20] [c000000000178e8c]
.ext4_discard_reservation+0x30/0xb4
[c0000000ede97bc0] [c00000000017c0b8] .ext4_release_file+0x54/0xbc
[c0000000ede97c50] [c0000000000de4b0] .__fput+0x114/0x214
[c0000000ede97d00] [c0000000000db2d8] .filp_close+0xb0/0xd8
[c0000000ede97d90] [c0000000000dbb20] .sys_close+0xc4/0x128
[c0000000ede97e30] [c00000000000872c] syscall_exit+0x0/0x40
uh-oh! some one just deleted it
Call Trace:
[c0000000e6b1f970] [c000000000010554] .show_stack+0x6c/0x1a0
(unreliable)
[c0000000e6b1fa10] [c00000000019db90]
.ext4_mb_discard_inode_preallocations+0x1d4/0x428
[c0000000e6b1fb20] [c000000000178e8c]
.ext4_discard_reservation+0x30/0xb4
[c0000000e6b1fbc0] [c00000000017c0b8] .ext4_release_file+0x54/0xbc
[c0000000e6b1fc50] [c0000000000de4b0] .__fput+0x114/0x214
[c0000000e6b1fd00] [c0000000000db2d8] .filp_close+0xb0/0xd8
[c0000000e6b1fd90] [c0000000000dbb20] .sys_close+0xc4/0x128
[c0000000e6b1fe30] [c00000000000872c] syscall_exit+0x0/0x40
-- 0:conmux-control -- time-stamp -- Jan/08/08 2:20:11 --
-- 0:conmux-control -- time-stamp -- Jan/08/08 2:38:19 --
(bot:conmon-payload) disconnected
reply other threads:[~2008-01-08 10:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20080108105341.GA11659@skywalker \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=adilger@sun.com \
--cc=bzzz@sun.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox