public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
* xfs_repair 2.9.4 threading/progress info missing?
@ 2007-11-08 11:27 James Braid
  2007-11-08 23:29 ` Barry Naujok
  0 siblings, 1 reply; 2+ messages in thread
From: James Braid @ 2007-11-08 11:27 UTC (permalink / raw)
  To: xfs


I just upgraded to xfsprogs 2.9.4 and it seems the multi-threading and
progress information is no longer being reported?

2.8.18:
        - creating 8 worker thread(s)
Phase 1 - find and verify superblock...
        - reporting progress in intervals of 15 minutes
Phase 2 - using internal log
        - zero log...
        - scan filesystem freespace and inode maps...

2.9.4:
Phase 1 - find and verify superblock...
Phase 2 - using internal log
        - zero log...
        - scan filesystem freespace and inode maps...
        - found root inode chunk

Have I just mis-compiled something? The progress information in particular
was REALLY useful on our bigger filesystems.

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: xfs_repair 2.9.4 threading/progress info missing?
  2007-11-08 11:27 xfs_repair 2.9.4 threading/progress info missing? James Braid
@ 2007-11-08 23:29 ` Barry Naujok
  0 siblings, 0 replies; 2+ messages in thread
From: Barry Naujok @ 2007-11-08 23:29 UTC (permalink / raw)
  To: James Braid, xfs

On Thu, 08 Nov 2007 22:27:09 +1100, James Braid <jamesb@loreland.org>  
wrote:

>
> I just upgraded to xfsprogs 2.9.4 and it seems the multi-threading and
> progress information is no longer being reported?
>
> 2.8.18:
>         - creating 8 worker thread(s)
> Phase 1 - find and verify superblock...
>         - reporting progress in intervals of 15 minutes
> Phase 2 - using internal log
>         - zero log...
>         - scan filesystem freespace and inode maps...
>
> 2.9.4:
> Phase 1 - find and verify superblock...
> Phase 2 - using internal log
>         - zero log...
>         - scan filesystem freespace and inode maps...
>         - found root inode chunk
>
> Have I just mis-compiled something? The progress information in  
> particular
> was REALLY useful on our bigger filesystems.

Hi,

It is sort of still there. With the performance improvements
in 2.9.4, the multithreading implementation was changed and
hidden from the user. A side effect of this change was the
progress info is now only visible when using the ag_stride
option. Depending on your drive layout, ag_stride may speed
up repair even further, especially concats. With other layouts,
try "-o ag_stride=1". I found on one of our RAIDs, that
actually doubled doubled the repair performance on a 5 way
stripe.

Progress info for normal runs will be reintroduced in the
near future and other output will be cleaned up a tad.

Regards,
Barry.

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2007-11-08 23:29 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-11-08 11:27 xfs_repair 2.9.4 threading/progress info missing? James Braid
2007-11-08 23:29 ` Barry Naujok

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox