| To: | xfs@xxxxxxxxxxx |
|---|---|
| Subject: | problem with latest xfsprogs progress code |
| From: | "James Braid" <jamesb@xxxxxxxxxxxx> |
| Date: | Wed, 17 Jan 2007 05:30:42 +1300 (NZDT) |
| Importance: | Normal |
| Reply-to: | jamesb@xxxxxxxxxxxx |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | SquirrelMail/1.4.9a |
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> |
|---|---|---|
| ||
| Previous by Date: | TAKE 956323 - File system block reservation mechanism is broken, David Chatterton |
|---|---|
| Next by Date: | Re: problem with latest xfsprogs progress code, James Braid |
| Previous by Thread: | [PATCH] fix extent length in xfs_io bmap, Utako Kusaka |
| Next by Thread: | Re: problem with latest xfsprogs progress code, James Braid |
| Indexes: | [Date] [Thread] [Top] [All Lists] |