From: Dave Jones <davej@redhat.com>
To: Jan Kara <jack@suse.cz>
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 10:52:18 -0400 [thread overview]
Message-ID: <20130717145218.GA27731@redhat.com> (raw)
In-Reply-To: <20130717125322.GA29294@quack.suse.cz>
On Wed, Jul 17, 2013 at 02:53:22PM +0200, Jan Kara wrote:
> 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...
It was running this.. https://github.com/kernelslacker/io-tests/blob/master/setup.sh
in a loop. After about 6 hours, that fell out. It made it all the way through
every test a few times, which is odd, as the test should be fairly deterministic.
Ah, I wasn't capturing the fsx seed. I'll do that on the next run.
Perhaps that will make it easier to reproduce.
Dave
next prev parent reply other threads:[~2013-07-17 14:52 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
2013-07-17 14:52 ` Dave Jones [this message]
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=20130717145218.GA27731@redhat.com \
--to=davej@redhat.com \
--cc=jack@suse.cz \
--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.