From: Stan Hoeppner <stan@hardwarefreak.com>
To: Bharathiraja P <raja@where2getit.com>, xfs@oss.sgi.com
Subject: Re: OS Upgrade Considerations For XFS Volume
Date: Thu, 27 Nov 2014 23:20:24 -0600 [thread overview]
Message-ID: <54780618.1000009@hardwarefreak.com> (raw)
In-Reply-To: <CANoQhnbjv08FVe0iRFff0fNMV7u7POY9kPtAhCbe_Vz=d8kPxg@mail.gmail.com>
On 11/27/2014 08:29 AM, Bharathiraja P wrote:
> Hi there,
>
> We recently upgraded our database system from OpenSuSE-11.4 to OpenSuSE-13.1
>
> Post the upgrade we are noticing load spikes on our database system.
>
> OpenSuSE 11.4 uses kernel-2.6.37 and OpenSuSE-13.1 uses kernel-3.11.10
>
> There seems to be some changes related to XFS in new kernel and I'm
> getting this error when I run xfs_logprint
The two major XFS defaults changes here are:
1. Delayed logging
2. inode64 allocator
Read about each. They should not be impacting performance of a DB
workload nor system load.
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2014-11-28 5:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-27 14:29 OS Upgrade Considerations For XFS Volume Bharathiraja P
2014-11-28 0:59 ` Dave Chinner
2014-11-28 5:20 ` Stan Hoeppner [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=54780618.1000009@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=raja@where2getit.com \
--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