From: "Barry Naujok" <bnaujok@melbourne.sgi.com>
To: 'Stephan Jansen' <jansen@astro.wisc.edu>, xfs@oss.sgi.com
Subject: RE: xfs_check - out of memory | xfs_repair - superblock error reading
Date: Tue, 19 Sep 2006 10:33:31 +1000 [thread overview]
Message-ID: <200609190027.KAA27712@larry.melbourne.sgi.com> (raw)
In-Reply-To: <8B10E861-C427-4F9F-B0C4-7A87DB77236B@astro.wisc.edu>
> -----Original Message-----
> From: xfs-bounce@oss.sgi.com [mailto:xfs-bounce@oss.sgi.com]
> On Behalf Of Stephan Jansen
> Sent: Tuesday, 19 September 2006 8:56 AM
> To: xfs@oss.sgi.com
> Subject: Re: xfs_check - out of memory | xfs_repair -
> superblock error reading
>
>
> I was just going to create a 3TB filesystem on a 32 bit system. So
> xfs_check will not work? How about xfs_repair? I assume that will
> work but would like to know beforehand.
Just to let you know, I'm currently working on memory optimisations for
xfs_repair and when it's released, it should work on your system. Memory
usage will grow with inode count and free space fragementation and not based
on filesystem size as it currently does.
The first set of changes have been done and are currently being tested.
next prev parent reply other threads:[~2006-09-19 0:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-18 13:19 xfs_check - out of memory | xfs_repair - superblock error reading christian gattermair
2006-09-18 14:41 ` linux-xfs
2006-09-19 10:03 ` christian gattermair
2006-09-19 15:02 ` Eric Sandeen
2006-09-20 15:35 ` christian gattermair
2006-09-18 22:23 ` David Chinner
2006-09-18 22:56 ` Stephan Jansen
2006-09-19 0:33 ` Barry Naujok [this message]
2006-09-19 7:56 ` Frank Hellmann
-- strict thread matches above, loose matches on Subject: below --
2006-09-19 13:19 christian gattermair
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=200609190027.KAA27712@larry.melbourne.sgi.com \
--to=bnaujok@melbourne.sgi.com \
--cc=jansen@astro.wisc.edu \
--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