From: Christoph Hellwig <hch@infradead.org>
To: Nathan Scott <nathans@sgi.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: ST alloc failures
Date: Fri, 2 Apr 2004 07:32:07 +0100 [thread overview]
Message-ID: <20040402073207.A31736@infradead.org> (raw)
In-Reply-To: <20040402051355.GA1604@frodo>; from nathans@sgi.com on Fri, Apr 02, 2004 at 03:13:55PM +1000
[linux-scsi is the right list for st problems, moving the thread there]
On Fri, Apr 02, 2004 at 03:13:55PM +1000, Nathan Scott wrote:
> Hi all,
>
> I'm seeing a bunch of large allocation attempts failing from
> the SCSI tape driver when doing dumps and restores ... (this
> is with a stock 2.6.4 kernel).
>
> xfsdump: page allocation failure. order:8, mode:0xd0
> Call Trace:
> [<c013982b>] __alloc_pages+0x33b/0x3d0
> [<c03805ac>] enlarge_buffer+0xdc/0x1b0
> [<c03819a3>] st_map_user_pages+0x33/0x90
> [<c037cf24>] setup_buffering+0xb4/0x160
This looks like the driver tries to pin down the userpages first
(st_map_user_pages) but then fails and needs to use an inkernel
buffer. Can you put some debug printks into st_map_user_pages
to see why it fails? The actual message is harmless, it's the
same thing we had in the XFS log code: It tries to allocate
an as large as possible buffer and if that fails tries the next
smaller power of two size. We should probably add an __GFP_NOWARN
here.
next parent reply other threads:[~2004-04-02 6:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040402051355.GA1604@frodo>
2004-04-02 6:32 ` Christoph Hellwig [this message]
2004-04-03 7:19 ` ST alloc failures Kai Makisara
2004-04-06 8:48 ` Nathan Scott
2004-04-06 19:09 ` Kai Makisara
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=20040402073207.A31736@infradead.org \
--to=hch@infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=nathans@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