All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Steigerwald <Martin@lichtvoll.de>
To: linux-xfs@oss.sgi.com
Cc: Linda Walsh <xfs@tlinx.org>
Subject: Re: XFS for lots of small files
Date: Sat, 24 May 2008 18:16:55 +0200	[thread overview]
Message-ID: <200805241816.56080.Martin@lichtvoll.de> (raw)
In-Reply-To: <4836135D.9050409@tlinx.org>


Hi Linda,

Am Freitag 23 Mai 2008 schrieb Linda Walsh:
> Martin Steigerwald wrote:
> > And there is quite some fragmentation on it:
> >
> > xfs_db> frag
> > actual 653519, ideal 587066, fragmentation factor 10.17%
>
> ----
> 	Not to disturb you, but are  you running xfs_fsr on a
> regular basis?

No, not yet. I had those bad experiences with xfs_fsr on a ck patchset 
patched kernel and after this I didn't try again. Its pretty sure that my 
file content corruption issues was related to the ck patchset as I was 
not able to reproduce it with a CFS or mainline kernel. But still I have 
been reluctant. I think, I give it a try after I made my backups.

> I have a shell script that runs in my 'cron.daily' that has two
> lines:
> ----
> #!/bin/bash
> ionice -c 3 /usr/sbin/xfs_fsr &
> -------
>
> I've never noticed fragmentation above 1% on my disks...but your
> mileage may vary ....

Lets see ;-)

Ciao,
-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7

  reply	other threads:[~2008-05-24 16:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-06 16:11 XFS for lots of small files Leszek Dubiel
2008-05-06 16:23 ` Nicolas KOWALSKI
2008-05-06 18:55 ` Martin Steigerwald
2008-05-23  0:44   ` Linda Walsh
2008-05-24 16:16     ` Martin Steigerwald [this message]
2008-05-25  3:25   ` Eric Sandeen
2008-05-25 11:38     ` Martin Steigerwald
2008-05-25 15:39       ` 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=200805241816.56080.Martin@lichtvoll.de \
    --to=martin@lichtvoll.de \
    --cc=linux-xfs@oss.sgi.com \
    --cc=xfs@tlinx.org \
    /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.