public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nathan Scott <nathans@sgi.com>
To: David Martinez Moreno <ender@debian.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Crashes and lockups in XFS filesystem (2.6.8-rc4).
Date: Thu, 19 Aug 2004 18:44:10 +1000	[thread overview]
Message-ID: <20040819084410.GA14750@frodo> (raw)
In-Reply-To: <200408181816.57940.ender@debian.org>

On Wed, Aug 18, 2004 at 06:16:57PM +0200, David Martinez Moreno wrote:
> 	Hello, I am getting persistent lockups that could be IMHO XFS-related. I 
> created a fresh XFS filesystem in a SCSI disk, with xfsprogs version 2.6.18.
> 
> 	Mounted /dev/sda1 under /mnt, after that, I have been copying lots of files 
> from /dev/md0, then run a find blabla -exec rm \{\{ \; over /mnt and then 
> voilà! the lockup:

Did /mnt run out of space while doing that?  Or nearly?  There's
a known issue with that area of the XFS code, in conjunction with
4K stacks at the moment - was that enabled in your .config?

Looks like something stamped on parts of the xfs_mount structure
for the filesystem mounted at /mnt, a stack overrun would explain
that and your subsequent oopsen.

cheers.

-- 
Nathan

  reply	other threads:[~2004-08-19  7:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-18 16:16 Crashes and lockups in XFS filesystem (2.6.8-rc4) David Martinez Moreno
2004-08-19  8:44 ` Nathan Scott [this message]
2004-08-19  8:39   ` David Martínez Moreno
2004-08-19 17:35   ` Random crashes (was Re: Crashes and lockups in XFS filesystem (2.6.8-rc4).) David Martinez Moreno
     [not found]   ` <200408192127.58996.ender@debian.org>
2004-08-20  8:47     ` Crashes and lockups in XFS filesystem (2.6.8-rc4 and 2.6.8.1-mm2) Nathan Scott

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=20040819084410.GA14750@frodo \
    --to=nathans@sgi.com \
    --cc=ender@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    /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