From: Christoph Hellwig <hch@infradead.org>
To: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Cc: linux-kernel@vger.kernel.org, debian-kernel@lists.debian.org
Subject: Re: Problem with XFS and/or VM deadlock in 2.6.8
Date: Wed, 22 Dec 2004 18:21:03 +0000 [thread overview]
Message-ID: <20041222182103.GA14586@infradead.org> (raw)
In-Reply-To: <20041222141600.GA26253@csclub.uwaterloo.ca>
On Wed, Dec 22, 2004 at 09:16:00AM -0500, Lennart Sorensen wrote:
> I have been having trouble with the filesystem apparently locking up on
> a P4 2.8GHz HT machine (1GB ram, dual 120G SATA in raid1 with LVM on
> top).
>
> It locks up when I try and delete a lot of small files at once.
> Yesterday I tried to go delete a build dir for gcc-3.3 and while waiting
> for that 1.1GB to be deleted, went to delete a few other source dirs.
> When it got down to about 38M left for gcc-3.3 it stopped getting any
> further and top just showed rm in state D. A few other rm's eventually
> hit that state too.
>
> When I went to reboot the machine to get it back to working normally, I
> noticed the console had a bunch of messages from XFS and the VM. So I
> saved the messages in the hopes someone can figure something out to make
> this go away.
>
> Kernel version: 2.6.8-1-686-smp v2.6.8-10 (Debian sarge/sid build).
All this should be fixed in 2.6.10-rc3. The XFS code in Debian's 2.6.8
is very much out of data and has various problems, but 2.6.8 is already
really old and the various required core code changes make it hard to
backport the XFS fixes.
next prev parent reply other threads:[~2004-12-22 18:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-22 14:16 Problem with XFS and/or VM deadlock in 2.6.8 Lennart Sorensen
2004-12-22 18:21 ` Christoph Hellwig [this message]
2004-12-22 18:29 ` Lennart Sorensen
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=20041222182103.GA14586@infradead.org \
--to=hch@infradead.org \
--cc=debian-kernel@lists.debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lsorense@csclub.uwaterloo.ca \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.