From: Dave Chinner <david@fromorbit.com>
To: Stan Hoeppner <stan@hardwarefreak.com>
Cc: "xfs@oss.sgi.com" <xfs@oss.sgi.com>,
Stefan Priebe <s.priebe@profihost.ag>
Subject: Re: suddenly slow writes on XFS Filesystem
Date: Wed, 9 May 2012 17:04:51 +1000 [thread overview]
Message-ID: <20120509070450.GP5091@dastard> (raw)
In-Reply-To: <4FAA153D.1030606@hardwarefreak.com>
On Wed, May 09, 2012 at 01:57:01AM -0500, Stan Hoeppner wrote:
> On 5/7/2012 3:05 PM, Stefan Priebe wrote:
> > Am 07.05.2012 18:36, schrieb Stan Hoeppner:
....
> >> What I would suggest is doing an xfsdump to a filesystem on another LUN
> >> or machine, expand the size of this LUN by 50% or more (I gather this is
> >> an external RAID), format it appropriately, then xfsrestore. This will
> >> eliminate your current free space fragmentation, and the 50% size
> >> increase will delay the next occurrence of this problem. If you can't
> >> expand the LUN, simply do the xfsdump/format/xfsrestore, which will give
> >> you contiguous free space.
> > But this will only help for a few month or perhaps a year.
>
> So you are saying your backup solution will fill up an additional 2.3TB
> in less than a year? In that case I'd say you have dramatically
> undersized your backup storage and/or are not using file compression to
> your advantage. And you're obviously not using archiving to your
> advantage or you'd not have the free space fragmentation issue because
> you'd be dealing with much larger files.
>
> So the best solution to your current problem, and one that will save you
> disk space and thus $$, is to use a backup solution that makes use of
> both tar and gzip/bzip2.
Why use the slow method? xfsdump will be much faster than tar. :)
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-05-09 7:04 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-06 9:01 suddenly slow writes on XFS Filesystem Stefan Priebe
2012-05-06 10:31 ` Martin Steigerwald
2012-05-06 10:33 ` Martin Steigerwald
2012-05-06 15:45 ` Stan Hoeppner
2012-05-06 19:25 ` Stefan Priebe
2012-05-07 1:39 ` Dave Chinner
2012-05-06 21:43 ` Martin Steigerwald
2012-05-07 6:40 ` Stefan Priebe - Profihost AG
2012-05-07 1:34 ` Dave Chinner
2012-05-07 6:39 ` Stefan Priebe - Profihost AG
2012-05-07 7:17 ` Dave Chinner
2012-05-07 7:22 ` Stefan Priebe - Profihost AG
2012-05-07 16:36 ` Stan Hoeppner
2012-05-07 19:08 ` Martin Steigerwald
2012-05-07 20:05 ` Stefan Priebe
2012-05-09 6:57 ` Stan Hoeppner
2012-05-09 7:04 ` Dave Chinner [this message]
2012-05-09 7:36 ` Stefan Priebe - Profihost AG
2012-05-09 7:49 ` Stan Hoeppner
2013-02-15 15:06 ` 32bit apps and inode64 Stefan Priebe - Profihost AG
2013-02-15 21:46 ` Ben Myers
2013-02-16 10:24 ` Stefan Priebe - Profihost AG
2013-02-17 21:33 ` Dave Chinner
2013-02-18 8:12 ` Stefan Priebe - Profihost AG
2013-02-18 22:06 ` Dave Chinner
2013-02-17 8:13 ` Jeff Liu
2013-02-19 19:11 ` Ben Myers
2012-05-07 23:42 ` suddenly slow writes on XFS Filesystem Dave Chinner
2012-05-07 8:21 ` Martin Steigerwald
2012-05-07 16:44 ` Stan Hoeppner
2012-05-07 8:31 ` Martin Steigerwald
2012-05-07 13:57 ` Stefan Priebe - Profihost AG
2012-05-07 14:32 ` Martin Steigerwald
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=20120509070450.GP5091@dastard \
--to=david@fromorbit.com \
--cc=s.priebe@profihost.ag \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox