From: Dave Chinner <david@fromorbit.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: Alan Piszcz <ap@solarrain.com>, xfs@oss.sgi.com
Subject: Re: 2.6.39.1: (2.6.35+ probably): delaylog bug
Date: Mon, 4 Jul 2011 10:47:26 +1000 [thread overview]
Message-ID: <20110704004726.GU561@dastard> (raw)
In-Reply-To: <alpine.DEB.2.02.1107031702380.13519@p34.internal.lan>
On Sun, Jul 03, 2011 at 05:24:09PM -0400, Justin Piszcz wrote:
> Hello,
>
> I help to support a system (similar to mine) with a 3ware 9750-24i4e
> and when you rm -rf a directory with too many files, the system will
> act lagged, lock up for periods of time and drop connections
> (including samba shares) to and from the host. Its so bad it cannot
> even talk to the UPS for example (ups: communications lost, e.g.
> from nut). This is pretty bad and I've remounted my XFS FS w/out
> delaylog but for the xfstests package, it really needs to test with
> a few million files in a directory or two, and you should easily be
> able to reproduce the problem.
http://oss.sgi.com/archives/xfs/2011-06/msg00259.html
FYI, the problem is not easy to reproduce - it requires a specific
set of conditions to exist with interrupt configuration (i.e. all on
the same CPU that the log IO completions are running) to expose the
workqueue priority inversion that the filesystem level issue
triggers.
> When the delaylog option is removed, the files are removed slowly,
> but there are no errors, SSH/samba connections do NOT drop, etc,
> please look into this, thanks.
http://oss.sgi.com/archives/xfs/2011-06/msg00463.html
http://oss.sgi.com/archives/xfs/2011-06/msg00473.html
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2011-07-04 0:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-03 21:24 2.6.39.1: (2.6.35+ probably): delaylog bug Justin Piszcz
2011-07-04 0:47 ` Dave Chinner [this message]
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=20110704004726.GU561@dastard \
--to=david@fromorbit.com \
--cc=ap@solarrain.com \
--cc=jpiszcz@lucidpixels.com \
--cc=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