From: Andre Noll <maan@systemlinux.org>
To: Sage Weil <sage@newdream.net>
Cc: Jim Schutt <jaschut@sandia.gov>,
"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: unstable branch: ls -l hang after write by 64 clients
Date: Wed, 25 May 2011 19:33:38 +0200 [thread overview]
Message-ID: <20110525173338.GI20417@systemlinux.org> (raw)
In-Reply-To: <Pine.LNX.4.64.1105250913340.29945@cobra.newdream.net>
[-- Attachment #1: Type: text/plain, Size: 841 bytes --]
On Wed, May 25, 09:16, Sage Weil wrote:
> > It's trivial to reproduce: Executing "ls -l" on one client while
> > another client is writing causes the ls command to hang indefinitely.
>
> This was recently fixed in the master branch, commit
> ee7fa813ef29890557f0b03bd3950d422484215d. It hasn't made it into any
> releases yet. I'll cherry-pick it into stable for 0.28.2.
>
> Please let me know if you continue to see this problem with that fix in
> place.
Nope. I'm now running the ceph master branch (fe955881) on all nodes
but the problem remains. Even after stopping the writer, the "ls -l"
hangs. Linux kernel version is plain 2.6.38.7 everywhere and the ceph
setup is fairly simple: 6 cosds, one cmon and one cmds.
Thanks
Andre
--
The only person who always got his work done by Friday was Robinson Crusoe
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-05-25 17:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-26 18:21 unstable branch: ls -l hang after write by 64 clients Jim Schutt
2010-10-26 19:25 ` Sage Weil
2010-10-26 21:30 ` Jim Schutt
2010-10-28 5:06 ` Sage Weil
2010-10-28 16:16 ` Jim Schutt
2010-10-29 1:06 ` Nat N
2010-10-29 2:12 ` Yehuda Sadeh Weinraub
2010-10-29 2:45 ` Nat N
2011-05-25 11:01 ` Andre Noll
2011-05-25 16:16 ` Sage Weil
2011-05-25 17:33 ` Andre Noll [this message]
2011-05-25 17:52 ` Sage Weil
2011-05-25 18:25 ` Andre Noll
2011-05-25 18:29 ` Sage Weil
2011-05-25 18:45 ` Andre Noll
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=20110525173338.GI20417@systemlinux.org \
--to=maan@systemlinux.org \
--cc=ceph-devel@vger.kernel.org \
--cc=jaschut@sandia.gov \
--cc=sage@newdream.net \
/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.