From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: ceph-devel@vger.kernel.org
Subject: Re: waiting for sub ops
Date: Fri, 11 May 2012 15:25:46 +0200 [thread overview]
Message-ID: <4FAD135A.10108@profihost.ag> (raw)
In-Reply-To: <4FACB96F.3050309@profihost.ag>
Hi,
all messages are always taling about snapc? I've no idea what this is.
Stefan
Am 11.05.2012 09:02, schrieb Stefan Priebe - Profihost AG:
> Hi,
>
> while doing some stress testing with bonnie++ i'm seeing always these
> messages accross all osd's here is just an example for osd.2.
>
> All machines are connected with 2x 1Gbit/s bonding mode 6 to a HP switch.
>
> 2012-05-11 08:58:52.752057 osd.2 192.168.0.102:6801/4798 3218 : [WRN]
> old request osd_op(mds.0.1:49546 200.00000027 [write 1643206~13552]
> 1.379675e3) v4 received at 2012-05-11 08:58:22.044033 currently waiting
> for sub ops
> 2012-05-11 08:58:52.752059 osd.2 192.168.0.102:6801/4798 3219 : [WRN]
> old request osd_op(client.4108.1:28755 10000008004.00000266 [write
> 0~4194304] 0.79b497c7 snapc 1=[]) received at 2012-05-11 08:58:22.026435
> currently waiting for sub ops
> 2012-05-11 08:58:52.752061 osd.2 192.168.0.102:6801/4798 3220 : [WRN]
> old request osd_op(client.4108.1:28762 10000008004.0000026d [write
> 0~4194304] 0.493cb0d4 snapc 1=[]) received at 2012-05-11 08:58:22.191536
> currently waiting for sub ops
> 2012-05-11 08:58:52.752064 osd.2 192.168.0.102:6801/4798 3221 : [WRN]
> old request osd_op(client.4108.1:28765 10000008004.00000270 [write
> 0~4194304] 0.b2f1b144 snapc 1=[]) received at 2012-05-11 08:58:22.290388
> currently waiting for sub ops
> 2012-05-11 08:58:52.752066 osd.2 192.168.0.102:6801/4798 3222 : [WRN]
> old request osd_op(client.4108.1:28774 10000008004.00000279 [write
> 0~4194304] 0.2373c652 snapc 1=[]) received at 2012-05-11 08:58:22.392604
> currently waiting for sub ops
> 2012-05-11 08:58:52.752068 osd.2 192.168.0.102:6801/4798 3223 : [WRN]
> old request osd_op(client.4108.1:28775 10000008004.0000027a [write
> 0~4194304] 0.24a58617 snapc 1=[]) received at 2012-05-11 08:58:22.455618
> currently waiting for sub ops
> 2012-05-11 08:58:52.752070 osd.2 192.168.0.102:6801/4798 3224 : [WRN]
> old request osd_op(client.4108.1:28777 10000008004.0000027c [write
> 0~4194304] 0.1c900a76 snapc 1=[]) received at 2012-05-11 08:58:22.527086
> currently waiting for sub ops
> 2012-05-11 08:58:53.752212 osd.2 192.168.0.102:6801/4798 3225 : [WRN]
> old request osd_op(client.4108.1:28808 10000008004.0000029b [write
> 0~4194304] 0.46c529aa snapc 1=[]) received at 2012-05-11 08:58:23.252258
> currently waiting for sub ops
>
> Stefan
next prev parent reply other threads:[~2012-05-11 13:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-11 7:02 waiting for sub ops Stefan Priebe - Profihost AG
2012-05-11 13:25 ` Stefan Priebe - Profihost AG [this message]
2012-05-13 0:13 ` Sage Weil
2012-05-13 0:15 ` Sage Weil
2012-05-13 18:04 ` Stefan Priebe
2012-05-14 4:28 ` Sage Weil
2012-05-14 6:36 ` Stefan Priebe - Profihost AG
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=4FAD135A.10108@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=ceph-devel@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.