From: Amon Ott <a.ott@m-privacy.de>
To: Sage Weil <sage@newdream.net>
Cc: Yehuda Sadeh Weinraub <yehuda.sadeh@dreamhost.com>,
"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: BUG at fs/inode.c
Date: Wed, 2 Nov 2011 09:53:44 +0100 [thread overview]
Message-ID: <201111020953.45095.a.ott@m-privacy.de> (raw)
In-Reply-To: <Pine.LNX.4.64.1111010907470.30839@cobra.newdream.net>
On Tuesday 01 November 2011 wrote Sage Weil:
> Can you capture a larger log segment? The hope is to catch the first
> use-after-free, and not the subsequent side-effects.
I still have the full kern.log here from boot till BUG, cleaned it up a bit
(no firewall lines, RSBAC stuff) and uploaded to
https://download.m-privacy.de/kern-full.log.bz2
Full ceph logging had been enabled as soon as possible, after boot and before
mounting ceph fs.
> Also, the below patch may help us parse the output with multiple threads.
Put in the patch, new kernel packages building now.
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
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-11-02 8:53 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
2011-11-01 8:23 ` Amon Ott
2011-11-01 16:51 ` Sage Weil
2011-11-02 8:53 ` Amon Ott [this message]
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=201111020953.45095.a.ott@m-privacy.de \
--to=a.ott@m-privacy.de \
--cc=ceph-devel@vger.kernel.org \
--cc=sage@newdream.net \
--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.