public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: David Chinner <dgc@sgi.com>
To: Emmanuel Florac <eflorac@free.fr>
Cc: Louis-David Mitterrand <vindex+lists-xfs@apartia.org>,
	xfs-dev <xfs-dev@sgi.com>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: running xfs_repair on large partitions
Date: Thu, 11 Oct 2007 07:57:33 +1000	[thread overview]
Message-ID: <20071010215733.GL995458@sgi.com> (raw)
In-Reply-To: <20071010191452.1fdad848@galadriel.home>

On Wed, Oct 10, 2007 at 07:14:52PM +0200, Emmanuel Florac wrote:
> Le Wed, 10 Oct 2007 16:33:38 +0200 vous écriviez:
> 
> > 1) it would be nice to have a way to know xfs_repair's version (-V ?),
> > when using it from a rescue disk I'm never sure if I should get a newer
> > one.
> 
> Did you try "xfs_repair -V" as you suggest? On my system, it replies with
> the version...
> 
> > 2) on a 32bit system, using xfsprogs version 2.9.0 , it seems xfs_repair
> > will fail if its process exceeds 4G. Is that right? Is there a way to
> > circumvent that limitation?
> 
> No, this is precisely what 32 bits mean. A 32 bits process can't address
> more than 2^32 bits, which is 4GB.

I think it's 2GB for a process by default on linux, because the other 2GB
is used by the kernel. The split is configurable IIRC.

> However I'm surprised you have this
> problem; I've xfs_repaired up to 16TB filesystem (maximum manageable with a
> 32 bits kernel ) without such problem.

Memory usage depends on the number of inodes in the filesystem as well.

Cheers,

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

      reply	other threads:[~2007-10-10 21:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-10 14:33 running xfs_repair on large partitions Louis-David Mitterrand
2007-10-10 17:14 ` Emmanuel Florac
2007-10-10 21:57   ` David Chinner [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=20071010215733.GL995458@sgi.com \
    --to=dgc@sgi.com \
    --cc=eflorac@free.fr \
    --cc=vindex+lists-xfs@apartia.org \
    --cc=xfs-dev@sgi.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