| To: | Louis-David Mitterrand <vindex+lists-xfs@xxxxxxxxxxx> |
|---|---|
| Subject: | Re: running xfs_repair on large partitions |
| From: | Emmanuel Florac <eflorac@xxxxxxx> |
| Date: | Wed, 10 Oct 2007 19:14:52 +0200 |
| Cc: | xfs-dev <xfs-dev@xxxxxxx>, xfs-oss <xfs@xxxxxxxxxxx> |
| In-reply-to: | <20071010143337.GA2815@xxxxxxxxxx> |
| Organization: | Moi. |
| References: | <20071010143337.GA2815@xxxxxxxxxx> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
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. 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.
--
Since we're all here, we must not be all there.
-- Bob "Mountain" Beck
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Crash on 2.6.21.7 Vanilla + DRBD 0.7, Louis-David Mitterrand |
|---|---|
| Next by Date: | Re: Recover fs, Emmanuel Florac |
| Previous by Thread: | running xfs_repair on large partitions, Louis-David Mitterrand |
| Next by Thread: | Re: running xfs_repair on large partitions, David Chinner |
| Indexes: | [Date] [Thread] [Top] [All Lists] |