From: Emmanuel Florac <eflorac@intellique.com>
To: xfs@oss.sgi.com
Subject: what is the FS size limit for xfs_repair ?
Date: Fri, 3 Oct 2008 17:04:52 +0200 [thread overview]
Message-ID: <20081003170452.50a7ec78@harpe.intellique.com> (raw)
After a system crash on a system with a 40TB XFS filesystem, xfs_repair
(32 bits binary, with a 64 bits 2.6.24 kernel) refused to work ("cannot
allocate block map, size xxx").
The 64 bits xfs_repair did the trick fine.
I tried to reproduce the problem today by corrupting a 22TB filesystem.
However, 32 bits xfs_repair repaired the 22 TB FS just fine in the very
same configuration (64 bits kernel, etc).
I thought the limit would be at 16TB (32 bits limit for a filesystem)
but obviously this isn't the case. Is the limitation higher (like 32
TB) or is it a bug of etch 4.0r4 xfs_repair?
--
----------------------------------------
Emmanuel Florac | Intellique
----------------------------------------
next reply other threads:[~2008-10-03 15:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-03 15:04 Emmanuel Florac [this message]
2008-10-03 15:23 ` what is the FS size limit for xfs_repair ? James Braid
2008-10-03 20:39 ` Emmanuel Florac
2008-10-04 0:22 ` Mark Goodwin
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=20081003170452.50a7ec78@harpe.intellique.com \
--to=eflorac@intellique.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