From: Jan Kara <jack@suse.cz>
To: Dave Jones <davej@redhat.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>, linux-ext4@vger.kernel.org
Subject: Re: ext4_da_release_space:1333: ext4_da_release_space: ino 12, to_free 1 with only 0 reserved data blocks
Date: Wed, 17 Jul 2013 14:53:22 +0200 [thread overview]
Message-ID: <20130717125322.GA29294@quack.suse.cz> (raw)
In-Reply-To: <20130716202533.GA16061@redhat.com>
On Tue 16-07-13 16:25:33, Dave Jones wrote:
> I've seen this happen a few times this week..
Thanks for report! Was this when fuzzing or just normal desktop load?
What is inode with inode number 12 on your filesystem sdb1? What IO happens
to it? Apparently some delalloc accounting went wrong somewhere and it's
searching for a needle in a haystack unless we have more details...
Honza
>
> EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
> EXT4-fs warning (device sdb1): ext4_da_release_space:1333: ext4_da_release_space: ino 12, to_free 1 with only 0 reserved data blocks
> ------------[ cut here ]------------
> WARNING: CPU: 3 PID: 798 at fs/ext4/inode.c:1334 ext4_da_invalidatepage+0x39e/0x3c0()
> Modules linked in: btrfs snd_hda_codec_realtek xor snd_hda_intel snd_hda_codec snd_pcm raid6_pq libcrc32c zlib_deflate snd_pag e_alloc snd_timer edac_core snd pcspkr serio_raw soundcore r8169 mii sr_mod cdrom pata_atiixp radeon backlight drm_kms_helper ttm
> CPU: 3 PID: 798 Comm: fsx Not tainted 3.11.0-rc1+ #12
> Hardware name: Gigabyte Technology Co., Ltd. GA-MA78GM-S2H/GA-MA78GM-S2H, BIOS F12a 04/23/2010
> ffffffff81a1bec7 ffff880126c81c18 ffffffff816b8a79 0000000000000000
> ffff880126c81c50 ffffffff81043efc ffff88010b753020 0000000000000002
> ffff88011bc237b0 ffff88011bc237b0 ffffea00045fbe00 ffff880126c81c60
> Call Trace:
> [<ffffffff816b8a79>] dump_stack+0x4e/0x82
> [<ffffffff81043efc>] warn_slowpath_common+0x8c/0xc0
> [<ffffffff81043fea>] warn_slowpath_null+0x1a/0x20
> [<ffffffff8124f1ae>] ext4_da_invalidatepage+0x39e/0x3c0
> [<ffffffff81152b6e>] truncate_inode_page+0x8e/0x90
> [<ffffffff81152f0a>] truncate_inode_pages_range+0x35a/0x650
> [<ffffffff81153272>] truncate_pagecache+0x52/0x80
> [<ffffffff81255f1d>] ext4_setattr+0x33d/0x840
> [<ffffffff811d90a8>] notify_change+0x1d8/0x350
> [<ffffffff811b91e9>] do_truncate+0x69/0x90
> [<ffffffff811b953e>] do_sys_ftruncate.constprop.17+0x10e/0x160
> [<ffffffff811b95ce>] SyS_ftruncate+0xe/0x10
> [<ffffffff816ca8d4>] tracesys+0xdd/0xe2
> ---[ end trace 267735bac62efc6a ]---
> EXT4-fs warning (device sdb1): ext4_da_release_space:1333: ext4_da_release_space: ino 12, to_free 1 with only 0 reserved data blocks
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
next prev parent reply other threads:[~2013-07-17 12:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-16 20:25 ext4_da_release_space:1333: ext4_da_release_space: ino 12, to_free 1 with only 0 reserved data blocks Dave Jones
2013-07-17 12:53 ` Jan Kara [this message]
2013-07-17 14:52 ` Dave Jones
2013-07-17 21:38 ` Jan Kara
2013-07-17 21:42 ` Dave Jones
2013-07-31 16:39 ` Dave Jones
2013-07-31 18:32 ` Jan Kara
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=20130717125322.GA29294@quack.suse.cz \
--to=jack@suse.cz \
--cc=davej@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@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.