All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Chinner <dgc@sgi.com>
To: Louis-David Mitterrand <vindex+lists-xfs@apartia.org>
Cc: xfs@oss.sgi.com, Linux XFS <linux-xfs@oss.sgi.com>
Subject: Re: libxfs_initbuf can't memalign 4096 bytes: Cannot allocate memory
Date: Mon, 28 Aug 2006 10:06:06 +1000	[thread overview]
Message-ID: <20060828000606.GF807830@melbourne.sgi.com> (raw)
In-Reply-To: <20060827205119.GA10325@apartia.fr> <20060827204222.GB12065@tuatara.stupidest.org> <17649.33701.520393.118416@base.ty.sabi.co.UK> <20060827072810.GA4098@apartia.fr>

On Sun, Aug 27, 2006 at 09:28:10AM +0200, Louis-David Mitterrand wrote:
> Package: xfsprogs
> Version: 2.8.11-1
> Followup-For: Bug #382935
> 
> Hello,
> 
> Using xfs_repair on a 2TB partition I get:
.....
> 	xfs_repair: libxfs_initbuf can't memalign 4096 bytes: Cannot allocate memory
> 
> 
> 
> -- System Information:
> Debian Release: testing/unstable
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (500, 'testing'), (499, 'experimental')
> Architecture: i386 (i686)

ia32, multi-terabyte filesystem, so as Peter pointed out:

On Sun, Aug 27, 2006 at 12:36:05PM +0100, Peter Grandi wrote:
> Most probably this is not a bug. The system probably does not
> have enough memory. "Cannot allocate memory" is probably what
> is happening. This has been discussed many times previously...
> 
>    http://OSS.SGI.com/archives/linux-xfs/2005-08/msg00045.html

This will be the problem.

On Sun, Aug 27, 2006 at 10:51:19PM +0200, Louis-David Mitterrand wrote:
> On Sun, Aug 27, 2006 at 01:42:22PM -0700, Chris Wedgwood wrote:
> > On Sun, Aug 27, 2006 at 09:28:10AM +0200, Louis-David Mitterrand wrote:
> > 
> > > 	xfs_repair: libxfs_initbuf can't memalign 4096 bytes: Cannot allocate memory
> > 
> > Not enough memory, try adding swap space if that's possible?  (BTW,
> > how much memory do you have in this case?)
> 
> I had 2GB RAM and a 300GB swap partition and was monitoring memory 
> consumption with "top": it never went over 3BG before failing.

It' won't matter how much swap you add - ia32 has a per-process memory
limit of 1-4GB RAM depending on kernel build options.

> With the 2.7.x version of xfs_repair found on a live CD distro, memory 
> consumption never exceeds 1GB on the same filesystem. Why has the 2.8.11 
> version become so greedy?

xfs_repair is undergoing a lot of change at the moment and so memory usage
may have blown out under some circumstances. Do you have figures on how much
more memory xfs_repair is using?

Cheers,

Dave.
-- 
Dave Chinner
Principal Engineer
SGI Australian Software Group

  parent reply	other threads:[~2006-08-28  0:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-27  7:28 libxfs_initbuf can't memalign 4096 bytes: Cannot allocate memory Louis-David Mitterrand
2006-08-27 11:36 ` Peter Grandi
2006-08-27 20:42 ` Chris Wedgwood
2006-08-27 20:51   ` Louis-David Mitterrand
2006-08-28  1:37     ` Peter Grandi
2006-08-28  0:06 ` David Chinner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-08-27  7:21 Louis-David Mitterrand
2006-08-28  5:57 ` Barry Naujok
2006-08-28 14:57   ` Louis-David Mitterrand
2006-08-28 15:04     ` Louis-David Mitterrand

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=20060828000606.GF807830@melbourne.sgi.com \
    --to=dgc@sgi.com \
    --cc=linux-xfs@oss.sgi.com \
    --cc=vindex+lists-xfs@apartia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.