From: Richard Scobie <r.scobie@clear.net.nz>
To: xfs@oss.sgi.com
Subject: Re: High Fragmentation with XFS and NFS Sync
Date: Sun, 03 Jul 2016 07:49:58 +1200 [thread overview]
Message-ID: <57781AE6.10605@clear.net.nz> (raw)
Nick Fisk wrote:
"So it looks like each parallel IO thread is being
allocated next to each other rather than at spaced out regions of the disk."
It's possible that the "filestreams" XFS mount option may help you out. See:
http://www.xfs.org/docs/xfsdocs-xml-dev/XFS_User_Guide/tmp/en-US/html/ch06s16.html
Regards,
Richard
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2016-07-02 19:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-02 19:49 Richard Scobie [this message]
2016-07-02 20:41 ` High Fragmentation with XFS and NFS Sync Nick Fisk
-- strict thread matches above, loose matches on Subject: below --
2016-07-02 8:52 Nick Fisk
2016-07-02 20:12 ` Darrick J. Wong
2016-07-02 21:00 ` Nick Fisk
2016-07-02 21:30 ` Nick Fisk
2016-07-02 22:02 ` Darrick J. Wong
2016-07-02 22:10 ` Nick Fisk
2016-07-03 12:34 ` Stefan Ring
2016-07-03 12:40 ` Nick Fisk
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=57781AE6.10605@clear.net.nz \
--to=r.scobie@clear.net.nz \
--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