From: Christoph Hellwig <hch@infradead.org>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: xfs@oss.sgi.com
Subject: Re: 3.0.1: xfs hang
Date: Thu, 25 Aug 2011 01:18:12 -0400 [thread overview]
Message-ID: <20110825051812.GC1869@infradead.org> (raw)
In-Reply-To: <alpine.DEB.2.02.1108201536510.14176@p34.internal.lan>
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?
Unfortunately your backtrace doesn't seem overly reliable, 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.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-08-25 5:18 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 [this message]
2011-08-25 7:01 ` Justin Piszcz
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=20110825051812.GC1869@infradead.org \
--to=hch@infradead.org \
--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