public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Carsten Aulbert <carsten@welcomes-you.com>
To: xfs@oss.sgi.com
Subject: How to damage a XFS-Filesystem?
Date: Wed, 02 Jan 2008 14:16:27 +0100	[thread overview]
Message-ID: <477B8EAB.8000703@welcomes-you.com> (raw)

Hi,

I have the following scenario:

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.

Thus I think I would need to:

(1) Fill the disk with files
(2) Damage the file sytem
(3) Run xfs_repair

My questions:

(1) Is there a nice tool which fills up a disk? I.e. I want to write
files with varying size and want to be able to check the validity
(md5,sha1...) of the files before and after the damage. I don't know if
it matters, but the number of entries per directory should also vary
greatly ;)

(2) I don't know if xfs_repair cares if the file system was damaged or
not. If it uses the same amount of time and memory on a fully intact
file system, I guess I don't have a question anymore. Otherwise: How can
a damage a xfs file system to make the job harder for xfs_repair. I
guess a simple dd if=/dev/random of=/dev/sdb1 with some offsets will not
be very effective, right?

(3) Anything else I need to be aware of?

Thanks for your patience (and yes, I have tried the archives for answers)

Cheers

Carsten

             reply	other threads:[~2008-01-02 13:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-02 13:16 Carsten Aulbert [this message]
2008-01-02 17:48 ` How to damage a XFS-Filesystem? Chris Wedgwood

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=477B8EAB.8000703@welcomes-you.com \
    --to=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