diff options
Diffstat (limited to 'results/classifier/zero-shot/108/other/1877418')
| -rw-r--r-- | results/classifier/zero-shot/108/other/1877418 | 46 |
1 files changed, 46 insertions, 0 deletions
diff --git a/results/classifier/zero-shot/108/other/1877418 b/results/classifier/zero-shot/108/other/1877418 new file mode 100644 index 000000000..948e58c7c --- /dev/null +++ b/results/classifier/zero-shot/108/other/1877418 @@ -0,0 +1,46 @@ +performance: 0.855 +other: 0.813 +graphic: 0.801 +device: 0.762 +files: 0.681 +semantic: 0.505 +vnc: 0.365 +debug: 0.356 +boot: 0.355 +socket: 0.319 +PID: 0.303 +permissions: 0.234 +network: 0.152 +KVM: 0.135 + +qemu-nbd freezes access to VDI file + +Mounted Oracle Virtualbox .vdi drive, which has GTP+BTRFS: +sudo qemu-nbd -c /dev/nbd0 /storage/btrfs.vdi + +Then I am operating on the btrfs filesystem and suddenly it freezes. + + + + + +I don't recommend you use VDI images in this way; we do not intend to support performant RW access; support for VDI images is there to convert to qcow2 or raw, generally. + +That said, some questions that might be interesting to know the answer to: + +- Try converting your VDI image to raw or qcow2 and mounting that instead. Does the conversion work successfully? Can you export that image via qemu-nbd and mount it? Does it work? +- Do non-BTRFS filesystems cause any problems? + + +I thought there were qemu-img for that. Since qemu-nbd allows mounting images a rw block devices, it's logical to think that you can use it for that purpose. Will try to reproduce again the issue in case it was a kernel problem instead of qemu-nbd. + +I agree, the program doesn't stop you from doing such things. It should work without error, but it might be slow. Just offering some advice you may not want to use it like this. + +Try to reproduce with qcow2 and qemu-nbd to see if the problem is with our support of the disk image format or if it's a problem with e.g. the access patterns and qemu-nbd itself, for instance. + +Tied again with same .vdi as block device for 4 hours, didn't experience further problems. don't know how to reproduce the issue again, even don't know if has been fixed with any software update. + +[Expired for QEMU because there has been no activity for 60 days.] + +[Expired for btrfs-progs (Ubuntu) because there has been no activity for 60 days.] + |