Try my test procedure described at http://bugs.archlinux.org/task/7778
; see if you can get it to happen with that. Running that procedure on
a virtual machine with the -ck kernel version 220.127.116.11.ck1-2 got it to
happen every time.
On 8/13/07, Martin Steigerwald <Martin@xxxxxxxxxxxx> wrote:
> Am Sonntag 12 August 2007 schrieb Martin Steigerwald:
> > > Hi!
> > >
> > > I ran test 42 and it completes successfully.
> > Hello,
> > I now read a post from someone who faced null byte areas in files after
> > xfs_fsr as well. And he writes that this problem is related to the
> > ck patchset:
> > http://bhhdoa.org.au/pipermail/ck/2007-August/008433.html
> > It may well be that it is related to the ck patchset in my case as
> > well. I did not know the exact kernel version anymore when I was using
> > xfs_fsr, since it took me 2 weeks to actually find about this
> > corruption. Well and when I ran xfsqa test I had a slighly newer kernel
> > was using the CFS scheduler instead of the ck patchset. Actually I
> > thought the other was using the CFS scheduler as well I didn't think
> > of it as having any relevance so I didn't look into that direction.
> > But now it seems that the problem actually is related ck patchset and
> > that I was using a kernel with ck patchset as well. I try to find the
> > time to run xfsqa test 42 for my latest ck patchset kernel to know for
> > sure.
> I ran test 42 on my last kernel with ck patchset -
> 18.104.22.168-tp42-ck2-sws2-2.2.10 - about 20 times, but it did not show any
> problem. Maybe I have to run it about a 1000 times, since about 0,1-0.5%
> of my files were affected when it failed and as it seems to me the tests
> only generates one fragmented file. Could it generate and check more
> fragmented files in one ago without to much work?
> Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
> GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
> ck mailing list - mailto: ck@xxxxxxxxxxxxxxx