xfs
[Top] [All Lists]

Re: problem with latest xfsprogs progress code

To: Klaus Strebel <klaus.strebel@xxxxxxx>
Subject: Re: problem with latest xfsprogs progress code
From: Eric Sandeen <sandeen@xxxxxxxxxxx>
Date: Wed, 17 Jan 2007 09:54:42 -0600
Cc: jamesb@xxxxxxxxxxxx, xfs@xxxxxxxxxxx
In-reply-to: <45AE2DDF.5000602@xxxxxxx>
References: <32920.193.203.83.22.1168965042.squirrel@xxxxxxxxxxxxxxxxx> <53858.193.203.83.22.1169031614.squirrel@xxxxxxxxxxxxxxxxx> <45AE2DDF.5000602@xxxxxxx>
Sender: xfs-bounce@xxxxxxxxxxx
User-agent: Thunderbird 1.5.0.9 (X11/20061219)
Klaus Strebel wrote:

>>> Running 2.8.18 xfs_repair on a largeish (65TB, ~70M inodes) filesystem on
>>> an x86_64 machine gives the following "progress" output:
>>>
>>> 12:15:36: process known inodes and inode discovery - 1461632 of 0 inod
>>> es done
>>> 12:15:36: Phase 3: elapsed time 14 minutes, 32 seconds - processed 100
>>> 571 inodes per minute
>>> 12:15:36: Phase 3: 0% done - estimated remaining time 3364 weeks, 3 da
>>> ys, 7 hours, 30 minutes, 45 seconds
>>>
>>> Is this a known bug?
> Hi James,
> 
> why do you think that this is a bug? You have an almost infinitely large
> filesystem, so the file-system check will also run for an almost
> infinitely long time ;-).
> 
> You see, not all that's possible is really desirable.

Well, while 65TB is impressive*, and repairing it quickly is indeed a
challenge, it probably still should not take 64+ years.  ;-)

Sounds like something is in fact going wrong.

-Eric

*it amuses me to see xfs users refer to nearly 100T as largeISH; clearly
 you all do not suffer from lowered expectations.  :)


<Prev in Thread] Current Thread [Next in Thread>