All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stewart Smith <stewart@flamingspork.com>
To: Kenneth Emerson <kenneth.emerson@gmail.com>, xfs@oss.sgi.com
Subject: Re: Defragging XFS File Systems
Date: Tue, 07 Jun 2011 15:48:05 +1000	[thread overview]
Message-ID: <8739jmjip6.fsf@flamingspork.com> (raw)
In-Reply-To: <BANLkTi=40mmE+DCbLcSWBwNQtWpP=N=tXw@mail.gmail.com>

On Mon, 6 Jun 2011 22:52:48 -0500, Kenneth Emerson <kenneth.emerson@gmail.com> wrote:
> I hadn't given much thought to fragmentation of my TV recordings volume
> (XFS) until reading through some MythTV-users threads recently that
> mentioned how fragmented an XFS file system could become.  After running
> xfs_db, I found out that my fs appeared to be quite bad:

MythTV can end up with fragmentation on XFS due to an fsync() call that
attempts to work raound limitations in ext3.

Workarounds include:
- allocsize mount parameter
- patch mythtv source not to fsync (you could easily write a patch that
only did fsync if not xfs... I've been meaning to do this for
years... not enough hours in day).
- run mythbackend with libeatmydata, thus disabling the fsync

-- 
Stewart Smith

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

  reply	other threads:[~2011-06-07  5:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-07  3:52 Defragging XFS File Systems Kenneth Emerson
2011-06-07  5:48 ` Stewart Smith [this message]
2011-06-07 12:05 ` Stan Hoeppner
     [not found]   ` <BANLkTikBSL8-eTAbF7a94ckLuZNyWCM=Eg@mail.gmail.com>
2011-06-08 21:00     ` Stan Hoeppner
2011-06-09  5:49       ` Michael Monnerie
2011-06-09  8:13         ` Stan Hoeppner
2011-06-09 10:12           ` Michael Monnerie
2011-06-09 18:24             ` Stan Hoeppner
2011-06-10 17:56               ` Dave Chinner
2011-06-11  1:12                 ` Stan Hoeppner

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=8739jmjip6.fsf@flamingspork.com \
    --to=stewart@flamingspork.com \
    --cc=kenneth.emerson@gmail.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.