All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcin Deranek <marcin.deranek@booking.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: stan@hardwarefreak.com, xfs@oss.sgi.com
Subject: Re: Performance degradation over time
Date: Thu, 11 Oct 2012 10:33:52 +0200	[thread overview]
Message-ID: <20121011103352.4ed8bbf5@booking.com> (raw)
In-Reply-To: <507586B4.6010201@sandeen.net>

Hi Eric,

On Wed, 10 Oct 2012 09:31:16 -0500
Eric Sandeen <sandeen@sandeen.net> wrote:

> Yep.  Ditch that; it overrides the maintained module that comes with
> the kernel itself.  See if that helps, first, I suppose.

I wasn't aware that stock kernel comes with xfs module. From my testing
looks like stock kernel module is still preferred over kmod-xfs:

# modinfo xfs
filename:       /lib/modules/2.6.18-308.el5/kernel/fs/xfs/xfs.ko
license:        GPL
description:    SGI XFS with ACLs, security attributes, large block/inode numbers, no debug enabled
author:         Silicon Graphics, Inc.
srcversion:     D37A003AFEE1A42BDD4DD56
depends:        
vermagic:       2.6.18-308.el5 SMP mod_unload gcc-4.1
module_sig:
883f3504f44471c48d0a1fbae482c4c11225a009e3fa1179850eea96ab882c910d750e88743fec5309d1ca09de3d81add6999f9dedc65f84a0d1e21293

Most likely due to historical reasons we still install kmod-xfs on our 
systems.
To be sure I have removed kmod-xfs, unmounted filesystem and removed
kernel module and them mounted filesystem again. Still seeing the very same
behaviour.

> Agreed that it would be good to know whether inode64 is in use.

No, we don't use any special mount options here.

> Let's start there (and with a modern xfs.ko) before we speculate
> further.

I guess next step would be to use inode64..
Regards,

Marcin

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

  reply	other threads:[~2012-10-11  8:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-10  8:51 Performance degradation over time Marcin Deranek
2012-10-10 13:17 ` Stan Hoeppner
2012-10-10 14:31   ` Eric Sandeen
2012-10-11  8:33     ` Marcin Deranek [this message]
2012-10-11  9:15       ` Marcin Deranek
2012-10-14 19:31         ` Peter Grandi
2012-10-10 23:37 ` Dave Chinner
2012-10-11  8:42   ` Marcin Deranek
  -- strict thread matches above, loose matches on Subject: below --
2016-03-08 14:09 Matthew Keeler
2016-03-08 16:32 ` Michal Kazior
2016-03-08 16:38   ` Matthew Keeler
2016-03-09  2:01     ` Matthew Keeler
2016-03-09  6:00       ` Michal Kazior
2016-03-09 12:46         ` Matthew Keeler
2016-03-17 11:21           ` Michal Kazior

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=20121011103352.4ed8bbf5@booking.com \
    --to=marcin.deranek@booking.com \
    --cc=sandeen@sandeen.net \
    --cc=stan@hardwarefreak.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.