From: Nathan Scott <nathans@sgi.com>
To: Kronos <kronos@kronoz.cjb.net>
Cc: linux-kernel@vger.kernel.org, linux-xfs@oss.sgi.com
Subject: Re: [2.6.8-rc2][XFS] Page allocation failure
Date: Thu, 29 Jul 2004 11:04:03 +1000 [thread overview]
Message-ID: <20040729010403.GC800@frodo> (raw)
In-Reply-To: <20040725173022.GA8345@dreamland.darkstar.lan>
Hi there,
On Sun, Jul 25, 2004 at 07:30:23PM +0200, Kronos wrote:
> ...
> It seems that XFS failed an order 5 allocation (not atomic) on the read
Hmm, that file is fragmented up the wazoo for some reason
(see the xfs_bmap -vv output on the file). Any chance you
know how it was written originally? In particular, was it
written with O_SYNC set? (or via a sync NFS mount?).
Thanks.
> path two times (there are 80 secs between the warnings). Can I assume
> that the FS is not harmed?
Yes you can (those were warning messages & not oopsen).
cheers.
--
Nathan
next prev parent reply other threads:[~2004-07-29 0:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-25 17:30 [2.6.8-rc2][XFS] Page allocation failure Kronos
2004-07-25 18:44 ` Chris Wedgwood
2004-07-29 1:04 ` Nathan Scott [this message]
2004-07-29 16:14 ` Kronos
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=20040729010403.GC800@frodo \
--to=nathans@sgi.com \
--cc=kronos@kronoz.cjb.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-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;
as well as URLs for NNTP newsgroup(s).