public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Roger Heflin <rheflin@atipa.com>
To: Dave Kleikamp <shaggy@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Apparent Deadlock with nfsd/jfs on 2.6.21.1 under bonnie.
Date: Tue, 29 May 2007 13:14:16 -0500	[thread overview]
Message-ID: <465C6D78.9030009@atipa.com> (raw)
In-Reply-To: <1180462215.10013.2.camel@kleikamp.austin.ibm.com>

Dave Kleikamp wrote:
> On Tue, 2007-05-29 at 12:16 -0500, Roger Heflin wrote:
> 
>> Dave,
>>
>> Apparently there appears to be another different similar lockup,
>> The MTBF has risen from 1-2 hours without that patch to >100 hours,
>> so I am fairly sure the patch did correct the original lockup, or
>> at the very least make it a lot less likely.
>>
>> I hit the machine across NFS for 5 days before it deadlocked, before
>> the patch I could only get an hour or two (2-4 different tries).
>>
>> Given that pdflush is "D" it does not appear to be an NFS issue.
>>
>> Included is the sysrq-t.
>>
>> This is with 2.6.21.1 + the JFSIO patch.
> 
> Is the system still in this state?  Can you cat /proc/fs/jfs/TxAnchor
> (if CONFIG_JFS_DEBUG is defined) and /proc/fs/jfs/txstats (if
> CONFIG_JFS_STATISTICS is defined)?
> 
> Thanks,
> Shaggy

Yes, the machine is still in that state.

Apparently I don't have either of those configured.

Anything else that we can collect before I rebuild the kernel with
those options setup?

                              Roger


  reply	other threads:[~2007-05-29 18:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4649BED9.6090207@atipa.com>
     [not found] ` <pan.2007.05.15.22.03.07.359081@linux.vnet.ibm.com>
2007-05-15 22:06   ` Apparent Deadlock with nfsd/jfs on 2.6.21.1 under bonnie Roger Heflin
2007-05-17 14:37   ` Roger Heflin
2007-05-17 14:48     ` Dave Kleikamp
2007-05-29 17:16       ` Roger Heflin
2007-05-29 18:10         ` Dave Kleikamp
2007-05-29 18:14           ` Roger Heflin [this message]
2007-05-29 18:30             ` Dave Kleikamp

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=465C6D78.9030009@atipa.com \
    --to=rheflin@atipa.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shaggy@linux.vnet.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox