linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mihai RUSU <dizzy@roedu.net>
To: Nathan Scott <nathans@sgi.com>
Cc: Linus Torvalds <torvalds@osdl.org>,
	Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Jens Axboe <axboe@suse.de>, Neil Brown <neilb@cse.unsw.edu.au>
Subject: Re: kernel BUG at mm/filemap.c:332!
Date: Fri, 5 Dec 2003 09:14:04 +0200 (EET)	[thread overview]
Message-ID: <Pine.LNX.4.56L0.0312050907350.26770@ahriman.bucharest.roedu.net> (raw)
In-Reply-To: <20031204211611.GA567@frodo>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Fri, 5 Dec 2003, Nathan Scott wrote:

> Was your filesystem near full?  There was a 2.4 deadlock fixed
> recently which could be what you hit there.

No it wasnt. It has a ~50% usage.

> You'll want a more recent 2.4 XFS kernel I suspect - Steve made
> several improvements in this area awhile back.

Ok. I know about improvements since XFS 1.1 and I assumed that using a 
recent (ie 2.6.0-test11) kernel the XFS bits with it whould be recent and 
such have those improvements.

> OK, looks like a default mkfs then (with an old-ish mkfs binary)?

True. Its a general /var partition, there waasnt any interest in giving 
mkfs paramteres for it.

> Newer mkfs' will give you a better AG layout and unwritten extents
> would be turned on - not relevent to this problem at all though.

Ok, noted :)

> An "ls -ld" and "xfs_bmap -v" on the directory would also provide
> me a bit more info to work with -- thanks!

$ ls -ld interfaces/
drwxr-xr-x    2 root     root        16384 Dec  5 09:06 interfaces/

$ /usr/sbin/xfs_bmap interfaces/
interfaces/:
        0: [0..7]: 25238288..25238295
        1: [8..31]: 25238304..25238327


> I have a few ideas about what this might be, let me stew on those
> for a bit and try a few things.

Thanks!

> -- 
> Nathan

- -- 
Mihai RUSU                                    Email: dizzy@roedu.net
GPG : http://dizzy.roedu.net/dizzy-gpg.txt    WWW: http://dizzy.roedu.net
                       "Linux is obsolete" -- AST
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQE/0DA+PZzOzrZY/1QRAnRoAJ9/VKw3okVloX1gTdayWXf1zxeJqACg1h9S
P9hQSHgK/K1CmlgT9/2L+H8=
=8PPr
-----END PGP SIGNATURE-----

      reply	other threads:[~2003-12-05  7:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-04 14:59 kernel BUG at mm/filemap.c:332! Mihai RUSU
2003-12-04 16:45 ` Linus Torvalds
2003-12-04 17:26   ` Mihai RUSU
2003-12-04 21:16     ` Nathan Scott
2003-12-05  7:14       ` Mihai RUSU [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=Pine.LNX.4.56L0.0312050907350.26770@ahriman.bucharest.roedu.net \
    --to=dizzy@roedu.net \
    --cc=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nathans@sgi.com \
    --cc=neilb@cse.unsw.edu.au \
    --cc=torvalds@osdl.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;
as well as URLs for NNTP newsgroup(s).