From: "Lukáš Czerner" <lczerner@redhat.com>
To: Mark Brown <ntdeveloper2002@yahoo.com>
Cc: "linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: Filesystem testing
Date: Thu, 6 Feb 2014 10:45:46 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.00.1402061040010.2248@localhost.localdomain> (raw)
In-Reply-To: <1391642427.40742.YahooMailNeo@web141002.mail.bf1.yahoo.com>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1617 bytes --]
On Wed, 5 Feb 2014, Mark Brown wrote:
> Date: Wed, 5 Feb 2014 15:20:27 -0800 (PST)
> From: Mark Brown <ntdeveloper2002@yahoo.com>
> To: "linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
> Subject: Filesystem testing
>
> Hello all,
> What are the most common testing tools used for stress testing ext4(or any file system..), and making sure the data (and metadata) that was written is correctly read back, operations that were done(whether usual R/W, but also others like truncate, stat,link, f* operations etc) did not cause problems or corruptions, do fscks if needed etc?
>
> Also, are there tools that can cause aborts underneath the file system, basically something in the mid layer that randomly drops IOs or something along those lines?
Yes, there is device mapper target dm-flakey (see
Documentation/device-mapper/dm-flakey.txt in linux kernel sources).
Xfstests does have infrastructure to use this target in its tests
(see tests 311, 321 and 322).
-Lukas
>
> I am looking for tests which can fully stress the system exercising the file system and also check for corruption.
>
> As an aside, I looked at xfstests, from what I could gather, it was started only for xfs, but there is ongoing work to make it work with ext4(and thus other posix FS?). If someone can point me to the documentation for xfstests and what it does, that would help. I could not find much.
>
> Thanks in advance.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2014-02-06 9:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-05 23:20 Filesystem testing Mark Brown
2014-02-06 2:00 ` Eric Sandeen
2014-02-06 3:12 ` Mark Brown
2014-02-06 3:31 ` Eric Sandeen
2014-02-06 23:16 ` Mark Brown
2014-02-07 4:48 ` Eric Sandeen
2014-02-06 9:45 ` Lukáš Czerner [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=alpine.LFD.2.00.1402061040010.2248@localhost.localdomain \
--to=lczerner@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=ntdeveloper2002@yahoo.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