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: Why does xfsdump encounter "WARNING: could not get list of non-root attributes for nondir ino nnnn: Cannot allocate memory (12)"?
Date: Sat, 31 Dec 2011 16:50:27 -0500	[thread overview]
Message-ID: <jdo01m$62j$1@dough.gmane.org> (raw)

Greetings,

Happy old year! ;-)

Running XFS on Ununtu 10.04 LTS, I have noticed more warnings with XFS dump the longer the system has been up. A reboot cuts down on the number of warnings xfsdump encounters. An example run of 
xfsdump is as follows:

/usr/sbin/xfsdump: using file dump (drive_simple) strategy
/usr/sbin/xfsdump: version 3.0.4 (dump format 3.0) - Running single-threaded
/usr/sbin/xfsdump: level 0 dump of ldslnx01:/srv
/usr/sbin/xfsdump: dump date: Sat Dec 31 15:25:42 2011
/usr/sbin/xfsdump: session id: b56b3cd7-30d6-44b4-a8a4-e131ee70b60d
/usr/sbin/xfsdump: session label: "data"
/usr/sbin/xfsdump: ino map phase 1: constructing initial dump list
/usr/sbin/xfsdump: ino map phase 2: skipping (no pruning necessary)
/usr/sbin/xfsdump: ino map phase 3: skipping (only one dump stream)
/usr/sbin/xfsdump: ino map construction complete
/usr/sbin/xfsdump: estimated dump size: 115786343168 bytes
/usr/sbin/xfsdump: WARNING: no media label specified
/usr/sbin/xfsdump: creating dump session media file 0 (media 0, file 0)
/usr/sbin/xfsdump: dumping ino map
/usr/sbin/xfsdump: dumping directories
/usr/sbin/xfsdump: dumping non-directory files
/usr/sbin/xfsdump: WARNING: could not get list of non-root attributes for nondir ino 234778: Cannot allocate memory (12)
/usr/sbin/xfsdump: WARNING: could not get list of non-root attributes for nondir ino 234813: Cannot allocate memory (12)
/usr/sbin/xfsdump: WARNING: could not get list of non-root attributes for nondir ino 1828443: Cannot allocate memory (12)
/usr/sbin/xfsdump: WARNING: could not get list of root attributes for nondir ino 1828443: Cannot allocate memory (12)
/usr/sbin/xfsdump: WARNING: could not get list of non-root attributes for nondir ino 2234019: Cannot allocate memory (12)
/usr/sbin/xfsdump: ending media file
/usr/sbin/xfsdump: media file size 115563111376 bytes
/usr/sbin/xfsdump: dump size (non-dir files) : 115472209824 bytes
/usr/sbin/xfsdump: dump complete: 4099 seconds elapsed
/usr/sbin/xfsdump: Dump Status: SUCCESS

Could someone please explain what is going on, and why a freshly rebooted system would result in less / no errors?

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:[~2011-12-31 21:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-31 21:50 Michael Lueck [this message]
2012-01-02 21:37 ` Why does xfsdump encounter "WARNING: could not get list of non-root attributes for nondir ino nnnn: Cannot allocate memory (12)"? Dave Chinner
2012-01-03  3:24   ` Michael Lueck
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='jdo01m$62j$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