From: Eric Sandeen <sandeen@sandeen.net>
To: Robert Johnson <robert.e.johnson@usm.edu>
Cc: xfs@oss.sgi.com
Subject: Re: Xfs errors:
Date: Mon, 04 Dec 2006 11:53:06 -0600 [thread overview]
Message-ID: <45746082.2090403@sandeen.net> (raw)
In-Reply-To: <200612041631.kB4GVdwV031915@mcvs4.priv.usm.edu>
Robert Johnson wrote:
> I have just installed and configured a xfs file system on Redhat AS4 server,
RHEL4 doesn't support xfs ;-)
> running on IBM eServer 366 platform. The file system was carved out of our
> EMC SAN, with Qlogic HBA dual port fiber channel cards. The error message is
> as follows:
>
> Dec 4 09:43:11 mail kernel: XFS: possible memory allocation deadlock in
> kmem_alloc (mode:0x250)
> Dec 4 09:43:14 mail kernel: XFS: possible memory allocation deadlock in
> kmem_alloc (mode:0x250)
> Dec 4 09:43:15 mail kernel: XFS: possible memory allocation deadlock in
> kmem_alloc (mode:0x250)
> Dec 4 09:44:44 mail kernel: XFS: possible memory allocation deadlock in
> kmem_alloc (mode:0x2d0)
You might have highly fragmented files, and xfs_fsr might help with this...
-Eric
prev parent reply other threads:[~2006-12-04 17:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-04 15:47 Xfs errors: Robert Johnson
2006-12-04 17:53 ` Eric Sandeen [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=45746082.2090403@sandeen.net \
--to=sandeen@sandeen.net \
--cc=robert.e.johnson@usm.edu \
--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