From: "Ragnar Kjørstad" <xfs@ragnark.vestdata.no>
To: linux-xfs@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: kernel deadlock; xfs
Date: Wed, 18 Jul 2001 19:57:23 +0200 [thread overview]
Message-ID: <20010718195723.A24237@vestdata.no> (raw)
Hi
We're experiencing a deadlock on a NFS-server using a XFS filesystem.
The kernel was originally running SGI XFS 1.0, but we've now tried 1.0.1
and the CVS-version (as of yesterday) - same problem.
The deadlock appear to be happening when accessing big files over NFS,
but we're not sure as we have not found a way to reproduce. There are no
kernel messages written to syslog, and the kernel debugger does not
start when pressing pause.
I assume that means the problem is inside an interrupt handler? Does
that exclude XFS as the potential problem?
The system is using aic7xxx SCSI adapters and hamachi gigabit ethernet
card.
We're going to try with a different filesystem and a different gigabit
card next, but if you have other suggestions for how to debug this,
please let us know.
--
Ragnar Kjorstad
Big Storage
reply other threads:[~2001-07-18 17:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20010718195723.A24237@vestdata.no \
--to=xfs@ragnark.vestdata.no \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.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