From: "Jim Schutt" <jaschut@sandia.gov>
To: Greg Farnum <greg@inktank.com>
Cc: Jim Schutt <jaschut@sandia.gov>,
ceph-devel@vger.kernel.org, Sage Weil <sage@inktank.com>,
Wido den Hollander <wido@42on.com>
Subject: Re: CephFS Space Accounting and Quotas
Date: Tue, 12 Mar 2013 16:34:01 -0600 [thread overview]
Message-ID: <513FAD59.4040205@sandia.gov> (raw)
In-Reply-To: <513E4124.9040309@sandia.gov>
On 03/11/2013 02:40 PM, Jim Schutt wrote:
>>> >> If you want I can attempt to duplicate my memory of the first
>>> >> test I reported, writing the files today and doing the strace
>>> >> tomorrow (with timestamps, this time).
>>> >>
>>> >> Also, would it be helpful to write the files with minimal logging, in
>>> >> hopes of inducing minimal timing changes, then upping the logging
>>> >> for the stat phase?
>> >
>> > Well that would give us better odds of not introducing failures of
>> > any kind during the write phase, and then getting accurate
>> > information on what's happening during the stats, so it probably
>> > would. Basically I'd like as much logging as possible without
>> > changing the states they system goes through. ;)
> Hmmm, this is getting more interesting...
>
> I just did two complete trials where I built a file system,
> did two sets of writes with minimal MDS logging, then
> turned MDS logging up to 20 with MDS ms logging at 1 for
> the stat phase.
>
> In each trial my strace'd find finished in < 10 seconds,
> and there were no slow stat calls (they were taking ~19 ms
> each).
>
> I'm going to do a third trial where I let things rest
> overnight, after I write the files. That delay is the
> only thing I haven't reproduced from my first trial....
As you suspected, that didn't make any difference either...
That trial didn't reproduce the slow stat behavior.
It turns out that the only way I can reliably reproduce
the slow stat behavior right now is to turn MDS debugging
up to 20.
I've got another set of logs with MDS debug ms = 1,
which I'll send via an off-list email.
I still haven't figured out what made that first test
exhibit this behavior, when I was using debug mds = 5.
-- Jim
>
> -- Jim
>
>
next prev parent reply other threads:[~2013-03-12 22:34 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <sfid-H20130305-170326-+024.05-1@marduk.tchpc.tcd.ie>
2013-03-05 17:03 ` CephFS First product release discussion Greg Farnum
2013-03-05 18:08 ` Wido den Hollander
2013-03-05 18:17 ` Greg Farnum
2013-03-05 18:28 ` Sage Weil
2013-03-05 18:36 ` Wido den Hollander
2013-03-05 18:48 ` Jim Schutt
2013-03-05 19:33 ` Sage Weil
2013-03-06 17:24 ` Wido den Hollander
2013-03-06 19:07 ` Jim Schutt
2013-03-06 19:13 ` CephFS Space Accounting and Quotas (was: CephFS First product release discussion) Greg Farnum
2013-03-06 19:58 ` CephFS Space Accounting and Quotas Jim Schutt
2013-03-06 20:21 ` Greg Farnum
2013-03-06 21:28 ` Jim Schutt
2013-03-06 21:39 ` Greg Farnum
2013-03-06 23:14 ` Jim Schutt
2013-03-07 0:18 ` Greg Farnum
2013-03-07 15:15 ` Jim Schutt
2013-03-08 22:45 ` Jim Schutt
2013-03-09 2:05 ` Greg Farnum
2013-03-11 14:47 ` Jim Schutt
2013-03-11 15:48 ` Greg Farnum
2013-03-11 16:48 ` Jim Schutt
2013-03-11 16:57 ` Greg Farnum
2013-03-11 20:40 ` Jim Schutt
2013-03-12 22:34 ` Jim Schutt [this message]
[not found] ` <513FAE0F.2010608@sandia.gov>
[not found] ` <BE627BF4B6E74BD49037D07821FC1DB9@inktank.com>
[not found] ` <5143AA84.50409@sandia.gov>
2013-03-15 23:17 ` Greg Farnum
2013-03-18 14:19 ` Jim Schutt
2013-03-06 21:42 ` Sage Weil
2013-03-06 5:01 ` [ceph-users] CephFS First product release discussion Neil Levine
[not found] ` <CANygib-U_MQi1TMmQuT_Q9MVwPfT+PzJwN=+BMcBK69WuRfu3w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-03-07 13:11 ` Félix Ortega Hortigüela
[not found] ` <E0B1337A572647BA9FCC0CE8CA946F42-4GqslpFJ+cxBDgjK7y7TUQ@public.gmane.org>
2013-03-07 11:54 ` Jimmy Tang
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=513FAD59.4040205@sandia.gov \
--to=jaschut@sandia.gov \
--cc=ceph-devel@vger.kernel.org \
--cc=greg@inktank.com \
--cc=sage@inktank.com \
--cc=wido@42on.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.