From: Ben Myers <bpm@sgi.com>
To: "Hammer, Marcus" <Marcus.Hammer@auma.com>
Cc: "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: Strange problems with xfs an SLESS11 SP2
Date: Fri, 11 May 2012 11:07:19 -0500 [thread overview]
Message-ID: <20120511160719.GA16099@sgi.com> (raw)
In-Reply-To: <CBD2D5A5.7C6B%Marcus.Hammer@auma.com>
Hey Marcus,
On Fri, May 11, 2012 at 02:41:41PM +0200, Hammer, Marcus wrote:
...
> So my question is what has changed from 2.6 kernels 3.0 kernels, which can
> explain this massive increase of metadata. (I did a defrag and we had
> sometimes over 140.000 extends to one inode).
>
> I am completely confused and do now know how to handle this. Perhaps somebody
> can help me to fix this problem or to understand what happens here…. I also
> talked with some netapp engineers and they said, I should ask at xfs.org.
You should also open a case with SuSE.
> One the filesystem are about 727 CISAM Files (IDX -> Index Files and DAT –>
> DATA Files). There are ten 15 GB Files on which some small content is often
> changed by the ERP system. The rest of the files are lower than 400 MB. We
> encounter this problem since the upgrade to SLES11 SP2 and the new kernel
> 3.0. (By the way we had to disable the transparent hugepages support in
> kernel 3.0, because of kernel crashes ;) - but this is a different story… )
So when you upgraded you left the filesystems in place. This is not a
dump/restore situation, and the increased fragmentation that you're seeing has
happened with subsequent runs of your application, correct?
-Ben
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-05-11 16:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-11 12:41 Strange problems with xfs an SLESS11 SP2 Hammer, Marcus
2012-05-11 16:07 ` Ben Myers [this message]
2012-05-11 16:36 ` Stefan Ring
2012-05-12 4:09 ` Eric Sandeen
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=20120511160719.GA16099@sgi.com \
--to=bpm@sgi.com \
--cc=Marcus.Hammer@auma.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.