All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Bharathiraja P <raja@where2getit.com>
Cc: xfs@oss.sgi.com
Subject: Re: OS Upgrade Considerations For XFS Volume
Date: Fri, 28 Nov 2014 11:59:30 +1100	[thread overview]
Message-ID: <20141128005930.GF27262@dastard> (raw)
In-Reply-To: <CANoQhnbjv08FVe0iRFff0fNMV7u7POY9kPtAhCbe_Vz=d8kPxg@mail.gmail.com>

On Thu, Nov 27, 2014 at 07:59:59PM +0530, 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.

And ...?

Is there any actual performance problem you've measured?

> 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
> 
> ==============
> sudo /usr/sbin/xfs_logprint /dev/mapper/pgsql-data
> raja's password:
> xfs_logprint:
> xfs_logprint: /dev/mapper/pgsql-data contains a mounted and writable

logprint is completely unreliable on an active and mounted
filesystem. It's not going to tell you anything useful about any
sort of performance issue - logprint is for debugging log recovery
problems....

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2014-11-28  0:59 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 [this message]
2014-11-28  5:20 ` Stan Hoeppner

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=20141128005930.GF27262@dastard \
    --to=david@fromorbit.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.