From: Sage Weil <sage@newdream.net>
To: "Talyansky, Roman" <roman.talyansky@sap.com>
Cc: "ceph-devel@lists.sourceforge.net" <ceph-devel@lists.sourceforge.net>
Subject: Re: Write operation is stuck
Date: Wed, 24 Feb 2010 10:43:34 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.1002241039500.17054@cobra.newdream.net> (raw)
In-Reply-To: <C6A64D82E3A5D24B949315CFBC1FA1AD072A3B5605@DEWDFECCR01.wdf.sap.corp>
Hi Roman,
On Wed, 24 Feb 2010, Talyansky, Roman wrote:
> Hi Sage,
>
> Besides the bug with the return value of write operation, the system hangs in a write operation.
> You can access the trace files of ceph servers at
> https://sapmats-de.sap-ag.de/download/download.cgi?id=DHTK24DYMIH8MJEYGMO5GT1GKDLBR9IJDKFAA3R0C4D1JGTYVW
The .tar.gz appears to be corrupt (gunzip complains)... :(
> The traces were collected without "debug mds = 20" in the configuration
> file. I still have the hang system available. I also run the systems to
> regenerate the hang with "debug mds = 20" defined.
>
> It would be great if we could have a chat to resolve the hang in about 4
> hours.
Sounds good. We should just be back from lunch, and will be in #ceph on
irc.oftc.net, or on jabber!
sage
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
next prev parent reply other threads:[~2010-02-24 18:43 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-10 21:26 Write operation is stuck Talyansky, Roman
2010-02-10 21:39 ` Sage Weil
2010-02-10 22:44 ` Talyansky, Roman
2010-02-10 22:49 ` Sage Weil
2010-02-16 17:27 ` Talyansky, Roman
2010-02-16 18:35 ` Sage Weil
2010-02-19 15:40 ` Talyansky, Roman
2010-02-19 18:39 ` Sage Weil
2010-02-23 14:11 ` Talyansky, Roman
2010-02-23 18:11 ` Yehuda Sadeh Weinraub
2010-02-24 13:34 ` Talyansky, Roman
2010-02-24 14:56 ` Sage Weil
2010-02-24 16:42 ` Talyansky, Roman
2010-02-24 18:43 ` Sage Weil [this message]
2010-02-24 23:21 ` Talyansky, Roman
2010-02-25 10:07 ` Talyansky, Roman
2010-08-27 12:18 Bogdan Lobodzinski
2010-08-27 15:42 ` Wido den Hollander
2010-08-27 16:09 ` Sage Weil
2010-08-30 15:32 ` Bogdan Lobodzinski
2010-08-30 19:39 ` Sage Weil
2010-08-31 7:56 ` Bogdan Lobodzinski
2010-09-01 15:21 ` Bogdan Lobodzinski
2010-09-01 19:29 ` Wido den Hollander
2010-09-03 15:02 ` Bogdan Lobodzinski
2010-09-03 17:10 ` Yehuda Sadeh Weinraub
2010-09-03 19:20 ` Yehuda Sadeh Weinraub
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=Pine.LNX.4.64.1002241039500.17054@cobra.newdream.net \
--to=sage@newdream.net \
--cc=ceph-devel@lists.sourceforge.net \
--cc=roman.talyansky@sap.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.