On 01/16/2013 12:32 AM, Tom Kusmierz wrote:
p.s. bizzare that when I "fill" ext4 partition with test data everything
check's up OK (crc over all files), but with Chris tool it gets
corrupted - for both Adaptec crappy pcie controller and for mother board
built in one. Also since courses of history proven that my testing
facilities are crap - any suggestion's on how can I test ram, cpu &
controller would be appreciated.
Similar issues had been the reason we wrote ql-fstest at q-leap. Maybe
you could try that? You can easily see the pattern of the corruption
with that. But maybe Chris' stress.sh also provides it.
Anyway, I yesterday added support to specify min and max file size, as
it before only used 1MiB to 1GiB sizes... It's a bit cryptic with bits,
though, I will improve that later.
https://bitbucket.org/aakef/ql-fstest/downloads
Cheers,
Bernd
PS: But see my other thread, using ql-fstest I yesterday entirely broke
a btrfs test file system resulting in kernel panics.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
