mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nathan Scott <nathans@sgi.com>
To: dag@bakke.com
Cc: linux-kernel@vger.kernel.org, linux-xfs@oss.sgi.com
Subject: Re: xfsdump hangs - 2.6.6 && 2.6.7-rc1-bk3
Date: Thu, 27 May 2004 06:37:40 +1000	[thread overview]
Message-ID: <20040527063740.A832024@wobbly.melbourne.sgi.com> (raw)
In-Reply-To: <20040526091315.17983.h012.c000.wm@mail.bakke.com.criticalpath.net>; from dag@bakke.com on Wed, May 26, 2004 at 09:13:14AM -0700

hi Dag,

On Wed, May 26, 2004 at 09:13:14AM -0700, dag@bakke.com wrote:
> 
> I experience hangs with xfsdump, when dumping my rootfs to a USB 2.0
> connected drive. The hangs are reproducible within 0.2-2 GB of dump, and
> always come together with one or two instances of :
> 
> pagebuf_get: failed to lookup pages
> 
>  xfssyncd      S C04F25E0     0   331      1           342   317 (L-TLB)
>  cfccbf9c 00000046 c1370610 c04f25e0 cfc31d60 c0238bec cfc31d98 c04fecd8 
>  00000031 00000000 cfccbfb0 00002773 37e96cbf 00000210 c13707b8 000a43c5 
>  cfccbfb0 00000000 00000000 c03d2ec3 cfccbfb0 000a43c5 00000000 c048e508 
>  Call Trace:
>  [<c0238bec>] pagebuf_rele+0x2c/0x120
>  [<c03d2ec3>] schedule_timeout+0x63/0xc0
>  [<c0121110>] process_timeout+0x0/0x10
>  [<c023f5e7>] xfssyncd+0x57/0xc0
>  [<c023f590>] xfssyncd+0x0/0xc0
>  [<c0103f4d>] kernel_thread_helper+0x5/0x18
>  
> Anyone?
> 

This looks like the result of an earlier error on the code
path at that initial warning there (known problem) - in the
current code there is a situation where we attempt metadata
readahead, cannot initialise a XFS buffer completely due to
low memory, but fail to correctly tear down that partially
created buffer when passing back the (recoverable) error.
We're working on a fix.

cheers.

-- 
Nathan

  reply	other threads:[~2004-05-26 20:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-26 16:13 dag
2004-05-26 20:37 ` Nathan Scott [this message]
2004-05-27  5:58 ` Nathan Scott
2004-05-26 17:01 dag
2004-05-27  8:09 dag
2004-05-27  8:18 ` Christoph Hellwig
2004-05-27 10:05 ` Nathan Scott

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=20040527063740.A832024@wobbly.melbourne.sgi.com \
    --to=nathans@sgi.com \
    --cc=dag@bakke.com \
    --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

all inboxes | Powered by JetHome®