From: Emmanuel Florac <eflorac@intellique.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: xfs corrupted
Date: Tue, 15 Oct 2013 21:52:51 +0200 [thread overview]
Message-ID: <20131015215251.4a527ddc@galadriel.home> (raw)
In-Reply-To: <F0730252-EF33-4452-957A-FA33DAD43913@colorremedies.com>
Le Tue, 15 Oct 2013 13:07:22 -0600 vous écriviez:
> That is very low RAM for a system with two big arrays attached. So if
> repair finds it needs to repair something it's going to take a long
> time.
> http://xfs.org/index.php/XFS_FAQ#Q:_Which_factors_influence_the_memory_usage_of_xfs_repair.3F
With a recent xfs_repair (3.x) it's large enough. I've checked
similar arrays recently on 4 GB machines in a couple of minutes.
--
------------------------------------------------------------------------
Emmanuel Florac | Direction technique
| Intellique
| <eflorac@intellique.com>
| +33 1 78 94 84 02
------------------------------------------------------------------------
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-10-15 19:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-15 8:41 xfs corrupted katmai
2013-10-15 18:34 ` Emmanuel Florac
2013-10-15 18:45 ` Stefanita Rares Dumitrescu
2013-10-15 19:07 ` Chris Murphy
2013-10-15 19:52 ` Emmanuel Florac [this message]
2013-10-15 19:34 ` Emmanuel Florac
2013-10-15 19:57 ` Stefanita Rares Dumitrescu
2013-10-15 20:05 ` Emmanuel Florac
2013-10-15 20:17 ` Stefanita Rares Dumitrescu
2013-10-15 20:18 ` Stefanita Rares Dumitrescu
2013-10-15 20:26 ` Dave Chinner
2013-10-16 12:23 ` Stefanita Rares Dumitrescu
2013-10-16 13:32 ` Stefanita Rares Dumitrescu
2013-10-16 17:33 ` Keith Keller
2013-10-16 22:16 ` Dave Chinner
2013-10-16 14:32 ` Stefanita Rares Dumitrescu
2013-10-16 20:52 ` Stefanita Rares Dumitrescu
2013-10-17 18:04 ` Stefanita Rares Dumitrescu
2013-10-15 20:02 ` Stefanita Rares Dumitrescu
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=20131015215251.4a527ddc@galadriel.home \
--to=eflorac@intellique.com \
--cc=lists@colorremedies.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