From: Dave Chinner <david@fromorbit.com>
To: "Cheung, Norman" <Norman.Cheung@kla-tencor.com>
Cc: "linux-xfs@oss.sgi.com" <linux-xfs@oss.sgi.com>
Subject: Re: Hung in D state during fclose
Date: Wed, 13 Feb 2013 09:21:50 +1100 [thread overview]
Message-ID: <20130212222150.GE26694@dastard> (raw)
In-Reply-To: <3542214BE3A3EF419F236DFE0F878BC905190D@BL2PRD0310MB374.namprd03.prod.outlook.com>
On Tue, Feb 12, 2013 at 09:06:03PM +0000, Cheung, Norman wrote:
> [NLC] Only 2 threads in D state. I need to wait for the next
> hang to take another stack trace. Is there any workaround I can
> reduce the frequencies of this hang. What about reducing the
> xfssyncd_centisecs? Or other knobs?
You need to isolate the cause of the hang before changing anything.
Twiddling random knobs won't improve the situation. Understand the
problem first, then take appropriate action.
> [NLC] 2 RAID controllers in the system, it hung from disks on
> both of them. One is SuperMicro 2208 and the other is LSI
> 9265-8I. I think both use the same chipset.
Does the filesystem that hangs always belong to the same controller?
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-02-12 22:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-12 6:17 Hung in D state during fclose Norman Cheung
2013-02-12 6:55 ` Dave Chinner
2013-02-12 7:01 ` Cheung, Norman
2013-02-12 10:20 ` Dave Chinner
2013-02-12 16:39 ` Cheung, Norman
2013-02-12 20:22 ` Dave Chinner
2013-02-12 21:06 ` Cheung, Norman
2013-02-12 22:21 ` Dave Chinner [this message]
2013-02-13 0:12 ` Cheung, Norman
2013-02-13 5:15 ` Dave Chinner
2013-02-14 4:53 ` Cheung, Norman
2013-02-26 19:41 ` Cheung, Norman
2013-02-26 20:31 ` Dave Chinner
-- strict thread matches above, loose matches on Subject: below --
2013-02-11 23:36 Cheung, Norman
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=20130212222150.GE26694@dastard \
--to=david@fromorbit.com \
--cc=Norman.Cheung@kla-tencor.com \
--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