All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Ring <stefanrin@gmail.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 18:36:09 +0200	[thread overview]
Message-ID: <CAAxjCEyXa-5aS=Pik8VgtnCM++hpraPsOsHR+-Lasa2znjgw9Q@mail.gmail.com> (raw)
In-Reply-To: <CBD2D5A5.7C6B%Marcus.Hammer@auma.com>

> The /disk5 is a frequent accessed xfs filesystem by the ERP system. The disk usage increased from 53% to 76-78%. But only the disk usage, the size of the files are completely the same.

Is it possible that this is caused by the aggressive pre-allocation?
There is a mount option (allocsize, I think) that allows you to
override this behavior.

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

  parent reply	other threads:[~2012-05-11 16:36 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
2012-05-11 16:36 ` Stefan Ring [this message]
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='CAAxjCEyXa-5aS=Pik8VgtnCM++hpraPsOsHR+-Lasa2znjgw9Q@mail.gmail.com' \
    --to=stefanrin@gmail.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.