Message-ID: <4C083AAD.80906@tlinx.org>
Date: Thu, 03 Jun 2010 16:28:45 -0700
From: "Linda A. Walsh" <xfs@tlinx.org>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.8.1.24) Gecko/20100228 Lightning/0.9 Thunderbird/2.0.0.24 Mnenhy/0.7.6.666
MIME-Version: 1.0
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?
References: <4BF7D787.4020903@tlinx.org> <20100525164244.GB18666@infradead.org>
In-Reply-To: <20100525164244.GB18666@infradead.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

FWIF -- upgrading to the latest tool set seems to have caused
these messages to "go away"...


Christoph Hellwig wrote:
> On Sat, May 22, 2010 at 06:09:27AM -0700, Linda A. Walsh wrote:
>> I've seen the problem in the dump below and was wondering what could  
>> possibly cause this -- because
>> shows loads of free memory (>20G)...  how much memory do non-root  
>> attributes take to dump?
> 
> 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?
>