From: Martin Steigerwald <Martin@lichtvoll.de>
To: xfs@oss.sgi.com
Subject: Re: High I/O waits
Date: Tue, 21 Oct 2014 09:45:24 +0200 [thread overview]
Message-ID: <1594296.7DZVsZW4j9@merkaba> (raw)
In-Reply-To: <5446001A.5000909@ocius.nl>
Am Dienstag, 21. Oktober 2014, 08:41:30 schrieb Stefan Bottelier | Ocius.nl:
> Hello,
Hi Stefan,
> We have change ore servers from Linux kernel 3.2.63 to 3.12.30, and now
> we have very more I/O waits on the block device.
> Are the some big changes in this version ? And we mount now with /sdb
> /srv but are the some mount options for better performance ?
>
> I hope somebody can help me with this.
Not yet, as your report lacks any details necessary to even make a guess what
the cause of your problem might be.
Please read
http://xfs.org/index.php/XFS_FAQ#Q:_What_information_should_I_include_when_reporting_a_problem.3F
and add the necessary information.
Ciao,
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2014-10-21 7:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-21 6:41 High I/O waits Stefan Bottelier | Ocius.nl
2014-10-21 7:45 ` Martin Steigerwald [this message]
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=1594296.7DZVsZW4j9@merkaba \
--to=martin@lichtvoll.de \
--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