All of lore.kernel.org
 help / color / mirror / Atom feed
From: Amon Ott <a.ott@m-privacy.de>
To: Yehuda Sadeh Weinraub <yehuda.sadeh@dreamhost.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: BUG at fs/inode.c
Date: Tue, 25 Oct 2011 16:35:10 +0200	[thread overview]
Message-ID: <201110251635.11474.a.ott@m-privacy.de> (raw)
In-Reply-To: <201110251038.06482.a.ott@m-privacy.de>

[-- Attachment #1: Type: text/plain, Size: 1436 bytes --]

On Tuesday 25 October 2011 wrote Amon Ott:
> On Monday 24 October 2011 wrote Yehuda Sadeh Weinraub:
> > Also, the client logs could help shedding a light on the issue. You
> > should have dynamic debugging turned on (CONFIG_DYNAMIC_DEBUG), and
> > something along the lines of:
> >
> > # mount -t debugfs none /sys/kernel/debug
> > # echo 'module ceph +p' > /sys/kernel/debug/dynamic_debug/control
> > # echo 'module libceph +p' > /sys/kernel/debug/dynamic_debug/control
>
> New kernels are building right now. Upgraded to 3.0.8, put in new
> ceph-client master fix 8ba1683acc83aee4bcab304844f8e60330e5ef1f and added
> CONFIG_DYNAMIC_DEBUG. This kernel will go into two big servers this time to
> give it some real load. Let's see whether I can reproduce there, too. If
> so, I will provide debug output as requested.

Finally, I could reproduce with debugging on and keep the system alive long 
enough to copy the kernel log. Attached are two examples of the BUG happening 
with surrounding Ceph logs. Before and after these extracts are some seconds 
without logging, so I assume they are complete.

Amon Ott
-- 
Dr. Amon Ott
m-privacy GmbH           Tel: +49 30 24342334
Am Köllnischen Park 1    Fax: +49 30 24342336
10179 Berlin             http://www.m-privacy.de

Amtsgericht Charlottenburg, HRB 84946

Geschäftsführer:
 Dipl.-Kfm. Holger Maczkowsky,
 Roman Maczkowsky

GnuPG-Key-ID: 0x2DD3A649

[-- Attachment #2: bug1.log.gz --]
[-- Type: application/x-gzip, Size: 19794 bytes --]

[-- Attachment #3: bug2.log.gz --]
[-- Type: application/x-gzip, Size: 7125 bytes --]

  reply	other threads:[~2011-10-25 14:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-24 10:39 BUG at fs/inode.c Amon Ott
2011-10-24 16:51 ` Yehuda Sadeh Weinraub
2011-10-25  8:38   ` Amon Ott
2011-10-25 14:35     ` Amon Ott [this message]
2011-11-01  8:23       ` Amon Ott
2011-11-01 16:51         ` Sage Weil
2011-11-02  8:53           ` Amon Ott
2011-11-02 14:23             ` Sage Weil
2011-11-05 17:06               ` Amon Ott
2011-11-06  5:33                 ` Sage Weil
2011-11-07 15:32                   ` Amon Ott

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=201110251635.11474.a.ott@m-privacy.de \
    --to=a.ott@m-privacy.de \
    --cc=ceph-devel@vger.kernel.org \
    --cc=yehuda.sadeh@dreamhost.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.