From: Eric Sandeen <sandeen@sandeen.net>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: xfs@oss.sgi.com
Subject: Re: xfs_db: out of memory (2.9.8)
Date: Sat, 25 Oct 2008 08:07:25 -0500 [thread overview]
Message-ID: <49031A0D.9040906@sandeen.net> (raw)
In-Reply-To: <alpine.DEB.1.10.0810250855430.5734@p34.internal.lan>
Justin Piszcz wrote:
>
> On Sat, 25 Oct 2008, Eric Sandeen wrote:
>
>> Justin Piszcz wrote:
>>> For the root partition I get "out of memory" when I try to check for
>>> fragmentation.
>>>
>>> # xfs_db -c frag -f /dev/md2
>>> xfs_db: out of memory
>> "-f" means "stored in a file"
>>
>>> # mount | grep "/dev/md2"
>>> /dev/md2 on / type xfs (rw,noatime)
>> It looks like you're cheating your way around:
>>
>> xfs_db: /dev/md2 contains a mounted filesystem
>>
>> fatal error -- couldn't initialize XFS library
>>
>> I'm not sure if that matters in this respect, though.
>>
>> You could use gdb to find out which allocation is failing.
>>
>>> # xfs_db -V
>>> xfs_db version 2.9.8
>>>
>>> Any idea?
>> Don't worry so much about that fragmentation stat? :)
>>
>> -Eric
>>
>>> Justin.
>>>
>>>
>
> .. but it used to work :(
if you can find out when it changed, maybe it can change back.
> Loaded symbols for /lib/libgcc_s.so.1
> Error while mapping shared library sections:
> ease: No such file or directory.
> (no debugging symbols found)
... so the output isn't so useful here
> mmap(NULL, 31221911552, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = -1 ENOMEM (Cannot allocate memory)
32G...
-Eric
prev parent reply other threads:[~2008-10-25 13:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-25 12:05 xfs_db: out of memory (2.9.8) Justin Piszcz
2008-10-25 12:50 ` Eric Sandeen
2008-10-25 12:58 ` Justin Piszcz
2008-10-25 13:07 ` Eric Sandeen [this message]
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=49031A0D.9040906@sandeen.net \
--to=sandeen@sandeen.net \
--cc=jpiszcz@lucidpixels.com \
--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