public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Lueck <mlueck@lueckdatasystems.com>
To: linux-xfs@oss.sgi.com
Subject: Re: Why does xfsdump encounter "WARNING: could not get list of non-root attributes for nondir ino nnnn: Cannot allocate memory (12)"?
Date: Mon, 02 Jan 2012 22:24:52 -0500	[thread overview]
Message-ID: <jdtsdv$2r1$1@dough.gmane.org> (raw)
In-Reply-To: <20120102213706.GQ23662@dastard>

Dave Chinner wrote:
> Memory is less fragmented, hence more likely to have a order-5
> allocation succeed. Try the patch below, and see if that helps.

More I was feeling a bit guilty that I was bouncing the machines to have the backup work without error... as "Linux Administrators NEVER reboot their boxes!"

I have a few too many things in the test tubes at the moment to take on custom patching a kernel build.

So, do these mean that there is anything wrong with the backup being made? Is the final SUCCESS return code in error?

Thank you for providing an explanation and patch.

Sincerely,

-- 
Michael Lueck
Lueck Data Systems
http://www.lueckdatasystems.com/

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2012-01-03  3:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-31 21:50 Why does xfsdump encounter "WARNING: could not get list of non-root attributes for nondir ino nnnn: Cannot allocate memory (12)"? Michael Lueck
2012-01-02 21:37 ` Dave Chinner
2012-01-03  3:24   ` Michael Lueck [this message]
2012-01-11  9:55   ` Christoph Hellwig
2012-01-11 10:03     ` Dave Chinner
2012-01-11 10:04       ` Christoph Hellwig
2012-01-11 10:14         ` Dave Chinner
2012-01-11 10:29           ` 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='jdtsdv$2r1$1@dough.gmane.org' \
    --to=mlueck@lueckdatasystems.com \
    --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