From: Nathan Scott <nscott@aconex.com>
To: Fong Vang <sudoyang@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: xfs_check running out of memory
Date: Fri, 04 Apr 2008 10:03:13 +1100 [thread overview]
Message-ID: <1207263793.21048.150.camel@edge.scott.net.au> (raw)
In-Reply-To: <4f52331f0804031556n1f00e435g3273c516aacc5d95@mail.gmail.com>
On Thu, 2008-04-03 at 15:56 -0700, Fong Vang wrote:
>
>
>
>
> xfs_check on one of my 64-bit server keeps running out of memory
> checking a
> 6.5TB file system with millions of files. xfsprogs is version 2.9.4
> One of
> the man pages online mentions a xfs_check64 version but I can't seem
> to find
> this anyway. Where can I find this tool?
>
Thats an IRIX remnant. On 64 bit Linux systems, xfs_db
(and hence xfs_check) will be built as 64 bit binaries.
Use xfs_repair -n, xfs_check does not scale (and will
hopefully be replaced by xfs_repair -n someday).
--
Nathan
next prev parent reply other threads:[~2008-04-03 23:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-03 22:56 xfs_check running out of memory Fong Vang
2008-04-03 23:03 ` Nathan Scott [this message]
2008-04-03 23:11 ` Fong Vang
2008-04-03 23:16 ` Nathan Scott
2008-04-03 23:23 ` Fong Vang
2008-04-03 23:33 ` Nathan Scott
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=1207263793.21048.150.camel@edge.scott.net.au \
--to=nscott@aconex.com \
--cc=sudoyang@gmail.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