[sheepdog-users] functional test 013 is failure in current master branch

[Hitoshi Mitake]

At Fri, 15 Aug 2014 10:09:26 +0900,
Hitoshi Mitake wrote:
> 
> At Thu, 14 Aug 2014 16:11:00 +0800,
> Ruoyu wrote:
> > 
> > There is no problem when test 013 is executed in stable branch.
> > That is to say, the error is only occurred in current master branch.
> > Is it related to VDI locking?
> > 
> > 013 Last Used:4s.  Test snapshot functionality - output mismatch (see 
> > 013.out.bad)
> > --- 013.out    2014-05-08 09:55:23.485439497 +0800
> > +++ 013.out.bad    2014-08-14 16:05:33.529083944 +0800
> > @@ -20,21 +20,30 @@
> >   512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
> >   read 512/512 bytes at offset 0
> >   512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
> > -read 512/512 bytes at offset 0
> > -512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
> > -read 512/512 bytes at offset 0
> > -512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
> > -read 512/512 bytes at offset 0
> > -512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
> > -read 512/512 bytes at offset 0
> > -512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
> > -read 512/512 bytes at offset 0
> > -512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
> > -read 512/512 bytes at offset 0
> > -512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
> > -read 512/512 bytes at offset 0
> > -512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
> > -read 512/512 bytes at offset 0
> > -512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
> > -read 512/512 bytes at offset 0
> > -512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
> > +cannot get vdi info, VDI is already locked, test 0 tag1
> > +qemu-io: can't open device sheepdog:test:tag1
> > +no file open, try 'help open'
> > +cannot get vdi info, VDI is already locked, test 0 tag2
> > +qemu-io: can't open device sheepdog:test:tag2
> > +no file open, try 'help open'
> > +cannot get vdi info, VDI is already locked, test 0 tag3
> > +qemu-io: can't open device sheepdog:test:tag3
> > +no file open, try 'help open'
> > +cannot get vdi info, VDI is already locked, test 0 tag4
> > +qemu-io: can't open device sheepdog:test:tag4
> > +no file open, try 'help open'
> > +cannot get vdi info, VDI is already locked, test 0 tag5
> > +qemu-io: can't open device sheepdog:test:tag5
> > +no file open, try 'help open'
> > +cannot get vdi info, VDI is already locked, test 0 tag6
> > +qemu-io: can't open device sheepdog:test:tag6
> > +no file open, try 'help open'
> > +cannot get vdi info, VDI is already locked, test 0 tag7
> > +qemu-io: can't open device sheepdog:test:tag7
> > +no file open, try 'help open'
> > +cannot get vdi info, VDI is already locked, test 0 tag8
> > +qemu-io: can't open device sheepdog:test:tag8
> > +no file open, try 'help open'
> > +cannot get vdi info, VDI is already locked, test 0 tag9
> > +qemu-io: can't open device sheepdog:test:tag9
> > +no file open, try 'help open'
> > Failures: 013
> > Failed 1 of 1 tests
> 
> Seems to be related to vdi locking. I'll dig in the problem
> later. Thanks for your report.

It was a problem in sheepdog driver of QEMU. Could you test QEMU of
the below branch?

https://github.com/sheepdog/qemu/tree/vdi-locking

Thanks,
Hitoshi

> 
> Thanks,
> Hitoshi
> 
> > 
> > 
> > -- 
> > sheepdog-users mailing lists
> > sheepdog-users at lists.wpkg.org
> > http://lists.wpkg.org/mailman/listinfo/sheepdog-users