From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs@oss.sgi.com, Dave Chinner <david@fromorbit.com>
Subject: Re: XFS Performance on NetApp
Date: Wed, 27 Oct 2010 01:57:03 +0200 [thread overview]
Message-ID: <201010270157.04276@zmi.at> (raw)
In-Reply-To: <20101026231007.GA32255@dastard>
[-- Attachment #1.1: Type: Text/Plain, Size: 1209 bytes --]
On Mittwoch, 27. Oktober 2010 Dave Chinner wrote:
> However, options that
> reduce filesystem fragmentation (e.g. allocsize) still have value in
> keeping the amount of metadata and ptotential seeks down...
Yes, but for NetApp: maybe. With this whole deduplication thingy, I
wonder if even such a simple assumption is true. And then some people
make a snapshot every hour, whichmeans your log will wander around on
the storage anyway. So it's best to "just use it".
Another thing just crosses my mind: on a thin provisioned system, would
the TRIM command be useful? Do such storages recognise this command? It
would be very clever, I think. Let's say you run xfs_fsr, that would
allow the upper layer to relaim unused space. Would that be the storage
or XenServer/VMware which needs to understand this command?
--
mit freundlichen Grüssen,
Michael Monnerie, Ing. BSc
it-management Internet Services
http://proteger.at [gesprochen: Prot-e-schee]
Tel: 0660 / 415 65 31
****** Radiointerview zum Thema Spam ******
http://www.it-podcast.at/archiv.html#podcast-100716
// Wir haben im Moment zwei Häuser zu verkaufen:
// http://zmi.at/langegg/
// http://zmi.at/haus2009/
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2010-10-26 23:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-26 22:33 XFS Performance on NetApp Michael Monnerie
2010-10-26 23:10 ` Dave Chinner
2010-10-26 23:57 ` Michael Monnerie [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=201010270157.04276@zmi.at \
--to=michael.monnerie@is.it-management.at \
--cc=david@fromorbit.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.