From: Louis-David Mitterrand <vindex+lists-xfs@apartia.org>
To: xfs@oss.sgi.com
Subject: libxfs_initbuf can't memalign 4096 bytes: Cannot allocate memory
Date: Sun, 27 Aug 2006 09:28:10 +0200 [thread overview]
Message-ID: <20060827072810.GA4098@apartia.fr> (raw)
Package: xfsprogs
Version: 2.8.11-1
Followup-For: Bug #382935
Hello,
Using xfs_repair on a 2TB partition I get:
Phase 1 - find and verify superblock...
Phase 2 - using internal log
- zero log...
- scan filesystem freespace and inode maps...
- found root inode chunk
Phase 3 - for each AG...
- scan and clear agi unlinked lists...
- process known inodes and perform inode discovery...
- agno = 0
- agno = 1
- agno = 2
- agno = 3
- agno = 4
- agno = 5
- agno = 6
- agno = 7
- agno = 8
- agno = 9
- agno = 10
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)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-6-debian-styx
Locale: LANG=en_CA, LC_CTYPE=fr_FR@euro (charmap=ISO-8859-15)
Versions of packages xfsprogs depends on:
ii libc6 2.3.6.ds1-4 GNU C Library: Shared libraries
ii libreadline5 5.1-7 GNU readline and history libraries
ii libuuid1 1.39-1 universally unique id library
xfsprogs recommends no packages.
-- no debconf information
next reply other threads:[~2006-08-27 9:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-27 7:28 Louis-David Mitterrand [this message]
2006-08-27 11:36 ` libxfs_initbuf can't memalign 4096 bytes: Cannot allocate memory 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
-- 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=20060827072810.GA4098@apartia.fr \
--to=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.