Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*problem\s+with\s+latest\s+xfsprogs\s+progress\s+code\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*problem\s+with\s+latest\s+xfsprogs\s+progress\s+code\s*$/: 15 ]

Total 15 documents matching your query.

1. problem with latest xfsprogs progress code (score: 1): Author:; Date: Wed, 17 Jan 2007 05:30:42 +1300 (NZDT); 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 in; /archives/xfs/2007-01/msg00106.html (7,798 bytes)
2. Re: problem with latest xfsprogs progress code (score: 1): Author:; Date: Thu, 18 Jan 2007 00:00:14 +1300 (NZDT); 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: tr; /archives/xfs/2007-01/msg00107.html (10,979 bytes)
3. Re: problem with latest xfsprogs progress code (score: 1): Author:; Date: Wed, 17 Jan 2007 15:08:31 +0100; James Braid schrieb: 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; /archives/xfs/2007-01/msg00108.html (11,966 bytes)
4. Re: problem with latest xfsprogs progress code (score: 1): Author:; Date: Wed, 17 Jan 2007 09:54:42 -0600; 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; /archives/xfs/2007-01/msg00109.html (9,294 bytes)
5. Re: problem with latest xfsprogs progress code (score: 1): Author:; Date: Thu, 18 Jan 2007 09:51:26 +1100; Barry is at linux.conf.au this week, he knows this code better than anyone else. Phase 3 is scanning the inodes in each allocation group, building up a map of filesystem blocks that are marked as use; /archives/xfs/2007-01/msg00111.html (10,752 bytes)
6. problem with latest xfsprogs progress code (score: 1): Author: ); Date: Wed, 17 Jan 2007 05:30:42 +1300 (NZDT); 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 in; /archives/xfs/2007-01/msg00346.html (7,798 bytes)
7. Re: problem with latest xfsprogs progress code (score: 1): Author: >; Date: Thu, 18 Jan 2007 00:00:14 +1300 (NZDT); 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: tr; /archives/xfs/2007-01/msg00347.html (10,979 bytes)
8. Re: problem with latest xfsprogs progress code (score: 1): Author: >; Date: Wed, 17 Jan 2007 15:08:31 +0100; James Braid schrieb: 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; /archives/xfs/2007-01/msg00348.html (11,966 bytes)
9. Re: problem with latest xfsprogs progress code (score: 1): Author: >; Date: Wed, 17 Jan 2007 09:54:42 -0600; 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; /archives/xfs/2007-01/msg00349.html (9,294 bytes)
10. Re: problem with latest xfsprogs progress code (score: 1): Author: >; Date: Thu, 18 Jan 2007 09:51:26 +1100; Barry is at linux.conf.au this week, he knows this code better than anyone else. Phase 3 is scanning the inodes in each allocation group, building up a map of filesystem blocks that are marked as use; /archives/xfs/2007-01/msg00351.html (10,752 bytes)
11. problem with latest xfsprogs progress code (score: 1): Author: "James Braid" <jamesb@xxxxxxxxxxxx>; Date: Wed, 17 Jan 2007 05:30:42 +1300 (NZDT); 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 in; /archives/xfs/2007-01/msg00586.html (7,798 bytes)
12. Re: problem with latest xfsprogs progress code (score: 1): Author: "James Braid" <jamesb@xxxxxxxxxxxx>; Date: Thu, 18 Jan 2007 00:00:14 +1300 (NZDT); 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: tr; /archives/xfs/2007-01/msg00587.html (11,073 bytes)
13. Re: problem with latest xfsprogs progress code (score: 1): Author: Klaus Strebel <klaus.strebel@xxxxxxx>; Date: Wed, 17 Jan 2007 15:08:31 +0100; James Braid schrieb: 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; /archives/xfs/2007-01/msg00588.html (12,122 bytes)
14. Re: problem with latest xfsprogs progress code (score: 1): Author: Eric Sandeen <sandeen@xxxxxxxxxxx>; Date: Wed, 17 Jan 2007 09:54:42 -0600; 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; /archives/xfs/2007-01/msg00589.html (9,436 bytes)
15. Re: problem with latest xfsprogs progress code (score: 1): Author: David Chatterton <chatz@xxxxxxxxxxxxxxxxx>; Date: Thu, 18 Jan 2007 09:51:26 +1100; Barry is at linux.conf.au this week, he knows this code better than anyone else. Phase 3 is scanning the inodes in each allocation group, building up a map of filesystem blocks that are marked as use; /archives/xfs/2007-01/msg00591.html (10,933 bytes)

Current List: 1 - 15
Page: [1]