From: "J.H." <warthog9@kernel.org>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: More issues found on kernel.org
Date: Mon, 18 Oct 2010 17:03:05 -0700 [thread overview]
Message-ID: <4CBCE039.2030501@kernel.org> (raw)
In-Reply-To: <20101018221528.GC31479@mail.oracle.com>
On 10/18/2010 03:15 PM, Joel Becker wrote:
> On Mon, Oct 18, 2010 at 12:15:19PM -0700, J.H. wrote:
>> Not that the current discussion on IMA, and the recent problems found
>> with XFS were enough, I've started seeing, rather regularly, what I've
>> reported in bugzilla
>>
>> https://bugzilla.kernel.org/show_bug.cgi?id=20702
>>
>> It looks like a double free is happening somewhere, and the issue
>> *SEEMS* to be limited to the dynamic web boxes (bugzilla, wiki's, etc)
>> and those are the only boxes I have running drbd and ocfs2.
>
> Obviously with no ocfs2 in the stack traces, it's hard to say
> anything from that perspective. Do you have any idea what file snmpd is
> closing?
Wasn't pointing the finger at ocfs2, or drbd for that matter, was noting
that was running on the box as those are the only two boxes with it, and
those are the boxes having issues right now. I'm at the point where I
have no idea *WHAT* was causing the problem just trying to get as much
info out there for debugging as possible.
As to what files snmpd was closing, no idea. I'm using snmpd both for
monitoring of the boxes, but HP's utilities are using it for a pile of
things as well, including disk monitoring and such. Could have been
just about anything unfortunately and I'm not sure there's a good way to
trap that if/when it happens again.
If I get to that state again is there anything that would be useful
(from a debugging perspective) to snag before the box falls over, I
might be able to get some sysrq requests back if anyone would find that
helpful, and might be able to poke around a bit, not sure how far I can
get before it becomes unusable yet.
- John 'Warthog9' Hawley
next prev parent reply other threads:[~2010-10-19 0:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-18 19:15 More issues found on kernel.org J.H.
2010-10-18 22:15 ` Joel Becker
2010-10-19 0:03 ` J.H. [this message]
2010-10-20 2:41 ` Robin Holt
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=4CBCE039.2030501@kernel.org \
--to=warthog9@kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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.