xfs
[Top] [All Lists]

Re: problem with latest xfsprogs progress code

To: xfs@xxxxxxxxxxx
Subject: Re: problem with latest xfsprogs progress code
From: "James Braid" <jamesb@xxxxxxxxxxxx>
Date: Thu, 18 Jan 2007 00:00:14 +1300 (NZDT)
Importance: Normal
In-reply-to: <32920.193.203.83.22.1168965042.squirrel@xxxxxxxxxxxxxxxxx>
References: <32920.193.203.83.22.1168965042.squirrel@xxxxxxxxxxxxxxxxx>
Reply-to: jamesb@xxxxxxxxxxxx
Sender: xfs-bounce@xxxxxxxxxxx
User-agent: SquirrelMail/1.4.9a
I'm now seeing the following output - it's been sitting at this point for
over 13 hours now... earlier versions of xfs_repair would finish quite a
bit faster. Any ideas whats going on?

        - 03:00:37: traversing filesystem - 0 of 55 allocation groups done
        - 03:15:37: traversing filesystem - 0 of 55 allocation groups done
        - 03:30:37: traversing filesystem - 0 of 55 allocation groups done
        - 03:45:37: traversing filesystem - 0 of 55 allocation groups done
        - 04:00:37: traversing filesystem - 0 of 55 allocation groups done
        - 04:15:37: traversing filesystem - 0 of 55 allocation groups done
        - 04:30:37: traversing filesystem - 0 of 55 allocation groups done
        - 04:45:37: traversing filesystem - 0 of 55 allocation groups done
        - 05:00:37: traversing filesystem - 0 of 55 allocation groups done
        - 05:15:37: traversing filesystem - 0 of 55 allocation groups done
        - 05:30:37: traversing filesystem - 0 of 55 allocation groups done
        - 05:45:37: traversing filesystem - 0 of 55 allocation groups done
        - 06:00:37: traversing filesystem - 0 of 55 allocation groups done
        - 06:15:37: traversing filesystem - 0 of 55 allocation groups done
        - 06:30:37: traversing filesystem - 0 of 55 allocation groups done
        - 06:45:37: traversing filesystem - 0 of 55 allocation groups done
        - 07:00:37: traversing filesystem - 0 of 55 allocation groups done
        - 07:15:37: traversing filesystem - 0 of 55 allocation groups done
        - 07:30:37: traversing filesystem - 0 of 55 allocation groups done
        - 07:45:37: traversing filesystem - 0 of 55 allocation groups done
        - 08:00:37: traversing filesystem - 0 of 55 allocation groups done
        - 08:15:37: traversing filesystem - 0 of 55 allocation groups done
        - 08:30:37: traversing filesystem - 0 of 55 allocation groups done
        - 08:45:37: traversing filesystem - 0 of 55 allocation groups done
        - 09:00:37: traversing filesystem - 0 of 55 allocation groups done
        - 09:15:37: traversing filesystem - 0 of 55 allocation groups done
        - 09:30:37: traversing filesystem - 0 of 55 allocation groups done
        - 09:45:37: traversing filesystem - 0 of 55 allocation groups done
        - 10:00:37: traversing filesystem - 0 of 55 allocation groups done
        - 10:15:37: traversing filesystem - 0 of 55 allocation groups done
        - 10:30:37: traversing filesystem - 0 of 55 allocation groups done



> 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?
>
> Thanks, James
>
>
>



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