public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Wedgwood <cw@f00f.org>
To: Carsten Aulbert <carsten@welcomes-you.com>
Cc: xfs@oss.sgi.com
Subject: Re: How to damage a XFS-Filesystem?
Date: Wed, 2 Jan 2008 09:48:05 -0800	[thread overview]
Message-ID: <20080102174805.GA32592@puku.stupidest.org> (raw)
In-Reply-To: <477B8EAB.8000703@welcomes-you.com>

On Wed, Jan 02, 2008 at 02:16:27PM +0100, Carsten Aulbert wrote:

> A file server with a 10 TB large xfs file system running on a RAID6
> SATA array, the server has 16 GB of memory. I want to test how long
> it would take to run xfs_repair on it and if the amount of memory is
> enough for that.

It depends on how fast the IO is and also how many files there are.

If you have a small number of really large files it's fairly fast, if
you have a large number of really small files (ie. email maildir) then
it tends to be much slower.

> (2) Damage the file sytem
> (3) Run xfs_repair

xfs_repair will run without having to damage the filesystem (though
if/when damaged it will probably be a little slower).

> Otherwise: How can a damage a xfs file system to make the job harder
> for xfs_repair.

Google for fsfuzzer.

> I guess a simple dd if=/dev/random of=/dev/sdb1 with some offsets
> will not be very effective, right?

If it misses the metadata, xfs_repair won't even notice.  If you whack
large chunks of metadata you might see considerable data loss.

      reply	other threads:[~2008-01-02 17:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-02 13:16 How to damage a XFS-Filesystem? Carsten Aulbert
2008-01-02 17:48 ` Chris Wedgwood [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=20080102174805.GA32592@puku.stupidest.org \
    --to=cw@f00f.org \
    --cc=carsten@welcomes-you.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