From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Alan Piszcz <ap@solarrain.com>, xfs@oss.sgi.com
Subject: Re: 3.0.1: xfs hang
Date: Thu, 25 Aug 2011 03:01:30 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1108250300060.14539@p34.internal.lan> (raw)
In-Reply-To: <20110825051812.GC1869@infradead.org>
On Thu, 25 Aug 2011, Christoph Hellwig wrote:
> On Sat, Aug 20, 2011 at 03:38:21PM -0400, Justin Piszcz wrote:
>> Hi,
>>
>> Forgot to remove 'delaylog' from my fstab on one of my machines,
>> while rm -rf a large directory with many files:
>
> Does it actually hand the machine, or do you get the warning and then
> work continues?
Hi,
Normally the work continues but delaylog's effect varies on different hardware.
For example on server HW it actually kills all network connections (ssh,etc)
if delaylog is set and you remove lots of files.
>
> Unfortunately your backtrace doesn't seem overly reliable
Would compiling with frame pointers help for future XFS/related items?
> , so it's kinda
> hard to figure out what is going on. There is nothing delaylog related
> in the provided one though. If it halfway matches what is going on it
> seems to be block I/O related.
Justin.
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2011-08-25 7:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-20 19:38 3.0.1: xfs hang Justin Piszcz
2011-08-25 5:18 ` Christoph Hellwig
2011-08-25 7:01 ` Justin Piszcz [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=alpine.DEB.2.02.1108250300060.14539@p34.internal.lan \
--to=jpiszcz@lucidpixels.com \
--cc=ap@solarrain.com \
--cc=hch@infradead.org \
--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