All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sam Lang <sam.lang@inktank.com>
To: Roman Hlynovskiy <roman.hlynovskiy@gmail.com>
Cc: Sage Weil <sage@inktank.com>, ceph-devel@vger.kernel.org
Subject: Re: ceph stability
Date: Thu, 20 Dec 2012 05:20:50 -1000	[thread overview]
Message-ID: <50D32CD2.7040309@inktank.com> (raw)
In-Reply-To: <CAD5ewrpM1W+pei4n7+0WBF6fyhdcbq7SkrgQjnCeZZwiBwK7rg@mail.gmail.com>

On 12/19/2012 10:02 PM, Roman Hlynovskiy wrote:
> Hello Sage,
>
> Yes, I can easily reproduce it.
>
> how can I open a bug on the tracker? I can't find the link for this.
> log is ready to be uploaded.

Hi Roman,

The bug tracker is at:  http://tracker.newdream.net/

Once you've created an account, you can jump to the project 'fs' through 
the scroll down bar on the right, and then click on the 'New Issue' tab.

-sam

> this is pure kernel client mount. my kernel on the client is
> 3.2.0-0.bpo.3-686-pae
>
> 2012/12/19 Sage Weil <sage@inktank.com>:
>> On Wed, 19 Dec 2012, Roman Hlynovskiy wrote:
>>> My second problem - I have 2 systems which mount ceph. Whenever I
>>> mount ceph on any other system it usually mounts but get stuck on
>>> stat* operations (i.e. simple ls -al will hang with read( from the
>>> ceph-mounted directory for ages). This kind of client stuck also
>>> affects two working clients. they also start to stuck on the stat*
>>> even after shutdown of the third client. so usually umount/mount or
>>> even reboot for existing clients solves the issue)
>>
>> If this is something you can easily reproduce, can you please run with
>>
>> [mds]
>>          debug mds = 20
>>          debug ms = 1
>>
>> in your ceph.conf and attach the resulting mds log to a bug in the
>> tracker?  We've seen this sort of thing in the past, but not recently.
>>
>> Is this the kernel client mount?  What version of the client (kernel) are
>> you running?
>>
>> Thanks!
>> sage
>>
>>
>>
>
>
>


  reply	other threads:[~2012-12-20 15:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-19  9:03 ceph stability Roman Hlynovskiy
2012-12-19 10:08 ` Joao Eduardo Luis
2012-12-19 10:58   ` Roman Hlynovskiy
2012-12-19 12:11     ` Joao Eduardo Luis
2012-12-19 13:26 ` Mark Nelson
2012-12-20  7:08   ` Roman Hlynovskiy
2012-12-20 14:31     ` Mark Nelson
2012-12-21 10:07       ` Amon Ott
2013-01-05  0:37         ` Gregory Farnum
2012-12-19 15:40 ` Sage Weil
2012-12-20  8:02   ` Roman Hlynovskiy
2012-12-20 15:20     ` Sam Lang [this message]
2012-12-21  4:49       ` Roman Hlynovskiy

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=50D32CD2.7040309@inktank.com \
    --to=sam.lang@inktank.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=roman.hlynovskiy@gmail.com \
    --cc=sage@inktank.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.