From: "Linda A. Walsh" <xfs@tlinx.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: xfsdump -- not enough memory to dump attributes? w/>20G free -- how much does it need?
Date: Wed, 26 May 2010 00:34:55 -0700 [thread overview]
Message-ID: <4BFCCF1F.7010701@tlinx.org> (raw)
In-Reply-To: <20100525164244.GB18666@infradead.org>
Christoph Hellwig wrote:
> The error comes directly from the libhandle listing routine, which
> is a straight forward wrapper around the kernel syscall in current
> xfsprogs.
>
> What xfsprogs version are you using? I noticed your xfsdump is
> rather old, so making sure you have recent XFS userspace and
> possibly also the kernel would help debugging this.
>
> Also can you check using strace if the ENOMEM comes directly from
> the attr_list_by_handle ioctl?
---
versions:
xfsprogs/xfsdump both at 3.0.1-2.1 from suse11.2 which would
likely be 3.0.1 with some patchlevel from suse.
kernel is 2.6.34 (vanilla).
strace would be pretty difficult considering how far it is into a dump
before it is triggered.
Maybe I should try getting updated tools and see
if it "goes away"...
looks like I need to build xfsprogs before xfsdump?
looks like best way to pull current ver is from .git.
will try rebuilding and see if I have any luck...
BTW -- how do you tell the version of the xfs progs from
the individual progs -- I'm going from the installed rpm
name, but if I build from the git, that won't be helpful.
I don't see a VERSION command in xfsdump/restore?
Is there one with any of the xfs tools?
tnx,
-linda
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-05-26 7:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-22 13:09 xfsdump -- not enough memory to dump attributes? w/>20G free -- how much does it need? Linda A. Walsh
2010-05-25 16:42 ` Christoph Hellwig
2010-05-26 3:01 ` Stewart Smith
2010-05-26 7:34 ` Linda A. Walsh [this message]
2010-06-03 23:28 ` Linda A. Walsh
2010-10-16 2:56 ` Michael Lueck
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=4BFCCF1F.7010701@tlinx.org \
--to=xfs@tlinx.org \
--cc=hch@infradead.org \
--cc=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