search for: qual03

...gdb /usr/bin/qemu-img `pidof qemu-img` and run this command: > (gdb) t a a bt to show the stack trace in all threads. If qemu-img is consuming CPU then it's probably not hung. I'm still interested to find out why fstrim didn't work. Can you run: guestfish --ro -d unc-srv-qual03 ><fs> run ><fs> part-list /dev/sda ><fs> part-list /dev/sdb ><fs> part-list /dev/sdc ><fs> part-list /dev/sdd (etc) I'd be interested to see if the partitions are unaligned, which is the only reason why fstrim should fail on NTFS. Rich. -- Richar...

...n this command: > > > (gdb) t a a bt > > to show the stack trace in all threads. > > If qemu-img is consuming CPU then it's probably not hung. > > I'm still interested to find out why fstrim didn't work. Can you run: > > guestfish --ro -d unc-srv-qual03 > ><fs> run > ><fs> part-list /dev/sda > ><fs> part-list /dev/sdb > ><fs> part-list /dev/sdc > ><fs> part-list /dev/sdd > (etc) > > I'd be interested to see if the partitions are unaligned, which is the only reason why fstrim...

...gdb /usr/bin/qemu-img `pidof qemu-img` and run this command: > (gdb) t a a bt to show the stack trace in all threads. If qemu-img is consuming CPU then it's probably not hung. I'm still interested to find out why fstrim didn't work. Can you run: guestfish --ro -d unc-srv-qual03 ><fs> run ><fs> part-list /dev/sda ><fs> part-list /dev/sdb ><fs> part-list /dev/sdc ><fs> part-list /dev/sdd (etc) I'd be interested to see if the partitions are unaligned, which is the only reason why fstrim should fail on NTFS. Rich. -- Richard...

...gdb /usr/bin/qemu-img `pidof qemu-img` and run this command: > (gdb) t a a bt to show the stack trace in all threads. If qemu-img is consuming CPU then it's probably not hung. I'm still interested to find out why fstrim didn't work. Can you run: guestfish --ro -d unc-srv-qual03 ><fs> run ><fs> part-list /dev/sda ><fs> part-list /dev/sdb ><fs> part-list /dev/sdc ><fs> part-list /dev/sdd (etc) I'd be interested to see if the partitions are unaligned, which is the only reason why fstrim should fail on NTFS. Rich. -- Richard...

...n this command: > > > (gdb) t a a bt > > to show the stack trace in all threads. > > If qemu-img is consuming CPU then it's probably not hung. > > I'm still interested to find out why fstrim didn't work. Can you run: > > guestfish --ro -d unc-srv-qual03 > ><fs> run > ><fs> part-list /dev/sda > ><fs> part-list /dev/sdb > ><fs> part-list /dev/sdc > ><fs> part-list /dev/sdd > (etc) > > I'd be interested to see if the partitions are unaligned, which is the only reason why fstrim...

On Tue, Oct 14, 2014 at 02:43:31PM +0000, VONDRA Alain wrote: > Rich, > The conversion did'nt finish, and I don't have any core dump. > The qemu-img seems to hang, but doesn't crash... Please connect gdb to the hung process and get a stack trace to find out where it's hanging. 'strace -p ...' output might also be enlightening, if it is not hung but doing

...ile = /tmp/v2v.UgUPSx/0a6404e0-2857-45e4-9322-c1ada5ae13fb/images/0123ddcd-f88d-43d0-b836-2cabe57beac3/d0fe6d79-b846-41ca-ac94-835b97488685 target_format = raw target_estimated_size = 42968862720 target_overlay = /var/tmp/v2vovle2fd4a.qcow2 target_overlay.ov_source = /data/big_export/IMAGES/UNC-SRV-QUAL03-6.img qemu-img convert -p -n -f qcow2 -O 'raw' '/var/tmp/v2vovle2fd4a.qcow2' '/tmp/v2v.UgUPSx/0a6404e0-2857-45e4-9322-c1ada5ae13fb/images/0123ddcd-f88d-43d0-b836-2cabe57beac3/d0fe6d79-b846-41ca-ac94-835b97488685' (57.03/100%) The qemu-img idles : 23338 root 20 0...

On Wed, Oct 15, 2014 at 03:23:39PM +0000, VONDRA Alain wrote: > I see only qemu-img consumming some CPU and MEM : > > 25897 qemu 20 0 5825976 2,429g 4368 S 5,6 32,2 603:09.34 qemu-kvm That's qemu, not qemu-img. > I have indeed, some nfs errors : > > [475747.296041] nfs: server 192.203.100.247 not responding, still trying > [475747.772022] nfs: server