From: Ric Wheeler <rwheeler@redhat.com>
To: Chris Mason <chris.mason@oracle.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: New data=ordered code pushed out to btrfs-unstable
Date: Sun, 20 Jul 2008 08:19:14 -0400 [thread overview]
Message-ID: <48832D42.6030204@redhat.com> (raw)
In-Reply-To: <1216428331.6932.82.camel@think.oraclecorp.com>
Chris Mason wrote:
> On Fri, 2008-07-18 at 18:35 -0400, Ric Wheeler wrote:
>
>> Chris Mason wrote:
>>
>>> On Fri, 2008-07-18 at 16:09 -0400, Ric Wheeler wrote:
>>>
>>>
>>>> Just to kick the tires, I tried the same test that I ran last week on
>>>> ext4. Everything was going great, I decided to kill it after 6 million
>>>> files or so and restart.
>>>>
>
> Well, it looks like I neglected to push all the changesets, especially
> the last one that made it less racey. So, I've just done another push,
> sorry. For the fs_mark workload, it shouldn't change anything.
>
> This code still hasn't really survived an overnight run, hopefully this
> commit will.
>
> -chris
>
>
>
The test is still running, but slowly, with a (slow) stream of messages
about:
Jul 19 10:55:38 localhost kernel: INFO: task btrfs:448 blocked for more
than 120 seconds.
Jul 19 10:55:38 localhost kernel: "echo 0 >
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jul 19 10:55:38 localhost kernel: btrfs D ffffffff8129c5b0
0 448 2
Jul 19 10:55:38 localhost kernel: ffff8100283dfc50 0000000000000046
0000000000000000 ffffffffa0514254
Jul 19 10:55:38 localhost kernel: ffff810012c061c0 ffffffff814b2280
ffffffff814b2280 ffff81000b5ce0a0
Jul 19 10:55:38 localhost kernel: 0000000000000000 ffff81003f182cc0
ffff81003fac0000 ffff81003f183010
Jul 19 10:55:38 localhost kernel: Call Trace:
Jul 19 10:55:38 localhost kernel: [<ffffffffa0514254>] ?
:btrfs:free_extent_state+0x69/0x6e
Jul 19 10:55:38 localhost kernel: [<ffffffff8127ff47>]
__mutex_lock_slowpath+0x6b/0xa2
Jul 19 10:55:38 localhost kernel: [<ffffffff8127fdd2>] mutex_lock+0x2f/0x33
Jul 19 10:55:38 localhost kernel: [<ffffffffa04f6e96>]
:btrfs:maybe_lock_mutex+0x29/0x2b
Jul 19 10:55:38 localhost kernel: [<ffffffffa04fae0c>]
:btrfs:btrfs_alloc_reserved_extent+0x2c/0x67
Jul 19 10:55:38 localhost kernel: [<ffffffffa0512106>] ?
:btrfs:btrfs_lookup_ordered_extent+0x139/0x148
Jul 19 10:55:38 localhost kernel: [<ffffffffa050635f>]
:btrfs:btrfs_finish_ordered_io+0x102/0x2a8
Jul 19 10:55:38 localhost kernel: [<ffffffffa0506666>]
:btrfs:btrfs_writepage_end_io_hook+0x10/0x12
Jul 19 10:55:38 localhost kernel: [<ffffffffa0516b62>]
:btrfs:end_bio_extent_writepage+0xbe/0x28d
Jul 19 10:55:38 localhost kernel: [<ffffffff810c6f5d>] bio_endio+0x2b/0x2d
Jul 19 10:55:38 localhost kernel: [<ffffffffa0500d19>]
:btrfs:end_workqueue_fn+0x103/0x110
Jul 19 10:55:38 localhost kernel: [<ffffffffa051b43c>]
:btrfs:worker_loop+0x63/0x13e
Jul 19 10:55:38 localhost kernel: [<ffffffffa051b3d9>] ?
:btrfs:worker_loop+0x0/0x13e
Jul 19 10:55:38 localhost kernel: [<ffffffff810460e3>] kthread+0x49/0x76
Jul 19 10:55:38 localhost kernel: [<ffffffff8100cda8>] child_rip+0xa/0x12
Jul 19 10:55:38 localhost kernel: [<ffffffff8104609a>] ? kthread+0x0/0x76
Jul 19 10:55:38 localhost kernel: [<ffffffff8100cd9e>] ? child_rip+0x0/0x12
Jul 19 10:55:38 localhost kernel:
ric
next prev parent reply other threads:[~2008-07-20 12:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-18 16:36 New data=ordered code pushed out to btrfs-unstable Chris Mason
2008-07-18 20:09 ` Ric Wheeler
2008-07-18 20:12 ` Chris Mason
2008-07-18 22:35 ` Ric Wheeler
2008-07-19 0:45 ` Chris Mason
2008-07-20 12:19 ` Ric Wheeler [this message]
2008-07-20 13:32 ` Chris Mason
2008-07-20 13:46 ` Ric Wheeler
2008-07-21 15:08 ` Chris Mason
[not found] ` <4884D578.7040901@redhat.com>
2008-07-21 18:35 ` Chris Mason
2008-07-21 19:23 ` Ric Wheeler
2008-07-25 13:15 ` Chris Mason
2008-07-28 19:52 ` Chris Mason
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=48832D42.6030204@redhat.com \
--to=rwheeler@redhat.com \
--cc=chris.mason@oracle.com \
--cc=linux-btrfs@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.