From: Olaf Weber <olaf@sgi.com>
To: crow al <al-john@hotmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: How to simulate journal corruption
Date: Mon, 13 Jul 2009 13:28:45 +0200 [thread overview]
Message-ID: <bzymy78rfde.fsf@fransum.emea.sgi.com> (raw)
In-Reply-To: <SNT109-W2390816D3EF297CE0D07DEEC220@phx.gbl> (crow al's message of "Mon, 13 Jul 2009 13:55:05 +0800")
crow al writes:
> Hi, there
> I'm a QA engineer from Cisco. I'm working on a test case concerning
> XFS journal playback failure, which needs to manually inject error
> to XFS.
> I did some google work but get no luck. Then I think maybe XFA-QA
> could give me some advice. That why I come to here.
> Is there anyone could tell me how to inject error into XFS or is
> there any tool could be used?
For clobbering a filesystem image in general you can use fsfuzz.
http://people.redhat.com/sgrubb/files/fsfuzzer-0.7.tar.gz
If log replay is of particular interest, you might want to modify that
code to target the XFS log in particular.
The XFS QA tests do not, IIRC, contain tests that deliberately trash
the XFS log, but there are some tests that exercise log replay, and
you may want to take a look at those to see ways to get an XFS
filesystem image with a non-empty log to replay.
Note that kernel-side, if log replay fails the expected/desired result
is that kernel won't mount the filesystem.
--
Olaf Weber SGI Phone: +31(0)30-6696752
Veldzigt 2b Fax: +31(0)30-6696799
Technical Lead 3454 PW de Meern Vnet: 955-7151
Storage Software The Netherlands Email: olaf@sgi.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-07-13 11:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-13 5:55 How to simulate journal corruption crow al
2009-07-13 11:28 ` Olaf Weber [this message]
2009-07-13 14:44 ` Eric Sandeen
2009-07-14 2:08 ` crow al
[not found] ` <SNT109-W27FBC11B3A147486A10FAAEC200@phx.gbl>
2009-07-15 8:02 ` Wentao Lv (wentalv)
2009-07-15 13:58 ` 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=bzymy78rfde.fsf@fransum.emea.sgi.com \
--to=olaf@sgi.com \
--cc=al-john@hotmail.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