From: Nathan Scott <nscott@aconex.com>
To: Michael Monnerie <michael.monnerie@is.it-management.at>
Cc: xfs@oss.sgi.com
Subject: Re: xfs_repair question: "wrong" order of AG checks OK?
Date: Thu, 12 Nov 2009 11:23:03 +1100 (EST) [thread overview]
Message-ID: <1047569616.363721257985383289.JavaMail.root@mail-au.aconex.com> (raw)
In-Reply-To: <200911120029.21845@zmi.at>
----- "Michael Monnerie" <michael.monnerie@is.it-management.at> wrote:
> On Mittwoch 11 November 2009 Nathan Scott wrote:
> > Could be xfs_repair running with multiple threads in parallel?
>
> Would it ever do that? There's no performance advantage in that, as
> that operation is disk I/O bound, isn't it?
Be worth reading the paper here:
http://xfs.org/index.php/XFS_Papers_and_Documentation
-> "Fixing XFS Filesystems Faster"
cheers.
--
Nathan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-11-12 0:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-11 15:31 xfs_repair question: "wrong" order of AG checks OK? Michael Monnerie
2009-11-11 22:17 ` Nathan Scott
2009-11-11 23:29 ` Michael Monnerie
2009-11-12 0:23 ` Nathan Scott [this message]
2009-11-12 0:52 ` Michael Monnerie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1047569616.363721257985383289.JavaMail.root@mail-au.aconex.com \
--to=nscott@aconex.com \
--cc=michael.monnerie@is.it-management.at \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox