From: dth@ncc1701.cistron.net (Danny ter Haar)
To: linux-kernel@vger.kernel.org
Subject: xfs problems in 2.6.9-rc4 ?
Date: Wed, 13 Oct 2004 09:41:38 +0000 (UTC) [thread overview]
Message-ID: <ckit8i$np4$1@news.cistron.nl> (raw)
On our usenet storage server (diablo setup) we are running
2.6.9-rc4 and we see a *lot* of this in dmesg:
xfs: possible memory allocation deadlock in kmem_alloc (mode:0xd0)
xfs: possible memory allocation deadlock in kmem_alloc (mode:0xd0)
printk: 2899 messages suppressed.
dth@spool1:~$ mount
/dev/hda1 on / type ext3 (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
tmpfs on /dev/shm type tmpfs (rw)
/dev/hda5 on /usr type ext3 (rw)
/dev/hda6 on /var type ext3 (rw)
/dev/hda7 on /extra type ext3 (rw)
/dev/md0 on /news type ext3 (rw,data=writeback)
/dev/sdb1 on /news/spool/news/P.00 type xfs (rw,noatime)
/dev/sdd1 on /news/spool/news/P.01 type xfs (rw,noatime)
/dev/sdb5 on /news/spool/news/P.02 type xfs (rw,noatime)
/dev/sdb6 on /news/spool/news/P.03 type xfs (rw,noatime)
/dev/sdb7 on /news/spool/news/P.04 type xfs (rw,noatime)
/dev/sdb8 on /news/spool/news/P.05 type xfs (rw,noatime)
/dev/sdd5 on /news/spool/news/P.06 type xfs (rw,noatime)
/dev/sdd6 on /news/spool/news/P.07 type xfs (rw,noatime)
/dev/sdd7 on /news/spool/news/P.08 type xfs (rw,noatime)
/dev/sdd8 on /news/spool/news/P.09 type xfs (rw,noatime)
.config & kern.log output @ http://dth.net/kernel/
Anyone has any hints where to look ?
Danny
--
All those who believe in psychokinesis, raise my hand.
next reply other threads:[~2004-10-13 9:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-13 9:41 Danny ter Haar [this message]
2004-10-13 9:56 ` xfs problems in 2.6.9-rc4 ? Miquel van Smoorenburg
2004-10-13 10:02 ` Danny ter Haar
2004-10-13 10:28 ` Christoph Hellwig
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='ckit8i$np4$1@news.cistron.nl' \
--to=dth@ncc1701.cistron.net \
--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 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.