The 'fsstress' test is probably what you are looking for. I've used it=
few times myself for filesystem testing, and it was able to "successful=
uncover bugs for me.
Robert V. Williamson <robbiew@...>
Linux Test Project
IBM Linux Technology Center
Phone: (512) 838-9295 T/L: 678-9295
Fax: (512) 838-4603
IRC: #ltp on freenode.irc.net
"Only two things are infinite, the universe and human stupidity, and I'=
not sure about the former." -Albert Einstein
"Travis, Mark" =
<mtravis@...> To: "'ltp-=
list@...'" <ltp-list@...> =
Sent by: cc: =
ltp-list-admin@... Subject: [LTP] =
Filesystem Resilience? =
05/27/2003 03:44 PM =
Hello.=A0 I'm looking for a good way to test that a filesystem comes ba=
clean after a dirty shutdown.=A0 I'm in the process of testing suitabil=
network raid with MD and ENBD (http://www.it.uc3m.es/~ptb/nbd/).=A0 The=
filesystem I'm using is JFS, and the raw devices come from LVM.=A0 I'm
filesystem agnostic.=A0 JFS seems fine so I'll use it unless there's a =
reason to switch.
Anyway, what I'd like to do is test how well my ENBD-exported device fa=
in the event of a dirty shutdown on the primary.=A0 Supposedly, the dat=
should be identical on both sides.=A0 From what I've tested so far usin=
simple scripts that write and sync data it has appeared to work pretty =
-- the network-accessible mirror comes up very nicely.=A0 However, what=
would like to do is put the system under the type of duress that would =
likely trigger such things as a corrupted journal or something else whi=
would make it difficult, if not impossible, to recover the filesystem a=
a dirty shutdown.
Is fsstress a good way to do this?=A0 Does anybody on the list use LTP =
this type of testing?
Thank you very much for any assistance!