From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: with ECARTIS (v1.0.0; list xfs); Wed, 17 Jan 2007 06:25:19 -0800 (PST) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.183]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id l0HEP8qw018463 for ; Wed, 17 Jan 2007 06:25:10 -0800 Message-ID: <45AE2DDF.5000602@gmx.net> Date: Wed, 17 Jan 2007 15:08:31 +0100 From: Klaus Strebel MIME-Version: 1.0 Subject: Re: problem with latest xfsprogs progress code References: <32920.193.203.83.22.1168965042.squirrel@colo.loreland.org> <53858.193.203.83.22.1169031614.squirrel@colo.loreland.org> In-Reply-To: <53858.193.203.83.22.1169031614.squirrel@colo.loreland.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: xfs-bounce@oss.sgi.com Errors-to: xfs-bounce@oss.sgi.com List-Id: xfs To: jamesb@loreland.org Cc: xfs@oss.sgi.com James Braid schrieb: > 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? 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. Ciao Klaus Btw. i wouldn't expect this xfs_repair run to finish without running out of memory :-(. -- Mit freundlichen Grüssen / best regards Klaus Strebel, Dipl.-Inform. (FH), mailto:klaus.strebel@gmx.net /"\ \ / ASCII RIBBON CAMPAIGN X AGAINST HTML MAIL / \