From: Chris Mason <chris.mason@oracle.com>
To: rwheeler@redhat.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 09:32:21 -0400 [thread overview]
Message-ID: <1216560741.6932.83.camel@think.oraclecorp.com> (raw)
In-Reply-To: <48832D42.6030204@redhat.com>
On Sun, 2008-07-20 at 08:19 -0400, Ric Wheeler wrote:
> 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:
>
Could you please grab the sysrq-w if this is still running?
-chris
next prev parent reply other threads:[~2008-07-20 13:32 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
2008-07-20 13:32 ` Chris Mason [this message]
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=1216560741.6932.83.camel@think.oraclecorp.com \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=rwheeler@redhat.com \
/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.