Re: VirtualBox 4.2.20_2 FreeBSD 9.2-RELEASE host multi CPU VM poudriere crash
On 01/10/2014 02:23 AM, Derek Schrock wrote: Error: Failed to mount the ports directory /usr/local/share/poudriere/bulk.sh: 5: Bad file descriptor Write failed: Broken pipe Have you tried a fsck -f on the disk? Julian signature.asc Description: OpenPGP digital signature
Re: VirtualBox 4.2.20_2 FreeBSD 9.2-RELEASE host multi CPU VM poudriere crash
Yes, also something I forgot to mention, the crash isn't instant, it
will take ~3-4 minutes until the system freezes and the console reboots.
I can watch the system create the reference jails via top (poudriere
uses cpdup to copy data).
On Fri, Jan 10, 2014 at 11:59:50AM +0100, Julian Stecklina wrote:
On 01/10/2014 02:23 AM, Derek Schrock wrote:
Error: Failed to mount the ports directory
/usr/local/share/poudriere/bulk.sh: 5: Bad file descriptor
Write failed: Broken pipe
Have you tried a fsck -f on the disk?
Julian
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to
freebsd-virtualization-unsubscr...@freebsd.org
Re: VirtualBox 4.2.20_2 FreeBSD 9.2-RELEASE host multi CPU VM poudriere crash
2014/1/10 Derek Schrock der...@lifeofadishwasher.com: Using VirtualBox 4.2.20_2 (emulators/virtualbox-ose) on a 9.2-RELEASE amd64 4 core (8 CPU with HT) host a FreeBSD 10.0-RC5 amd64 (also tested with 3 and 4) VM with 4 allocated CPUs will repeatedly crashes when I try to build a pkg repo with poudriere (ports-mgmt/poudriere) via the bulk command. From the VM: root@freebsd10testing:~ # kldstat #VirtualBox additions loaded (tested with/without) Id Refs AddressSize Name 19 0x8020 15f0310 kernel 21 0x81a12000 22d50vboxguest.ko 31 0x81a35000 543 vboxvideo.ko 41 0x81a36000 16d6cdrm.ko root@freebsd10testing:~ # sysctl hw.ncpu hw.ncpu: 4 root@freebsd10testing:~ # uname -a FreeBSD freebsd10testing 10.0-RC5 FreeBSD 10.0-RC5 #0 r260430: Wed Jan 8 05:10:04 UTC 2014 r...@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 root@freebsd10testing:~ # poudriere bulk -j testing www/firefox Creating the reference jail... done Mounting system devices for testing-default Mounting ports/packages/distfiles Mounting packages from: /usr/local/poudriere/data/packages/testing-default Logs: /usr/local/poudriere/data/logs/bulk/testing-default/2014-01-09_19h23m11s /etc/resolv.conf - /usr/local/poudriere/data/build/testing-default/ref/etc/resolv.conf Starting jail testing-default Calculating ports order and dependencies pkg package missing, skipping sanity Cleaning the build queue Building 145 packages using 4 builders Starting/Cloning builders mount_nullfs: /usr/local/poudriere/data/build/testing-default/03/usr/ports: Device not configured Error: Failed to mount the ports directory /usr/local/share/poudriere/bulk.sh: 5: Bad file descriptor Write failed: Broken pipe At this point the ssh session dies (Write failed: Broken pipe) and the VM restarts (watching the console via VNC). The crash appears to occur during the building of the reference jails (one per CPU - 4). I don't see anything in /var/log/messages, /var/crash/ is empty, and savecore doesn't dump any core files. I've tested this with 2, 3, 4, 5, and 6 CPUs allocated to the VM and it crashes every time. The only way I can have the VM not crash is with 1 allocated CPU. I believe there's an issue with VirtualBox and FreeBSD 10.0 VM when the VM has multiple CPUs. I don't think this is a poudriere issue however it's the only way I've been able to crash the VM. I've tried extracting multiple ports trees to different locations at the same time thinking it's a disk issue because of the above Device not configured (The/a disk disappears?) error, the VM didn't crash. I've tried the same command with a FreeBSD 9.2-RELEASE amd64 4 CPU VM under the same host with out any failure/crashes. Could anyone confirm this with a multi-CPU VM and FreeBSD 10.0RC3/4/5 or recommend any methods on how to debug this issue? First of all attach serial console to VM and see if there is any kernel messages printed upon crash. Also there is a possibly similar problem: http://lists.freebsd.org/pipermail/freebsd-stable/2014-January/076772.html ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org -- Mikhail ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
Re: VirtualBox 4.2.20_2 FreeBSD 9.2-RELEASE host multi CPU VM poudriere crash
On Fri, Jan 10, 2014 at 05:18:24PM +0400, Mikhail Tsatsenko wrote: First of all attach serial console to VM and see if there is any kernel messages printed upon crash. Also there is a possibly similar problem: http://lists.freebsd.org/pipermail/freebsd-stable/2014-January/076772.html ___ FreeBSD/amd64 (freebsd10testing) (ttyu0) login: Jan 10 08:35:48 freebsd10testing su: dereks to root on /dev/pts/0 panic: handle_written_inodeblock: live inodedep 0xf80004eb1a00 cpuid = 0 KDB: stack backtrace: #0 0x808e7dd0 at kdb_backtrace+0x60 #1 0x808af8b5 at panic+0x155 #2 0x80ad3c85 at softdep_disk_write_complete+0x1595 #3 0x80934cb0 at bufdone_finish+0x30 #4 0x80934b18 at bufdone+0x78 #5 0x809346c2 at biodone+0xe2 #6 0x8081c561 at g_io_schedule_up+0x1b1 #7 0x8081ca5d at g_up_procbody+0x6d #8 0x8088198a at fork_exit+0x9a #9 0x80c758ce at fork_trampoline+0xe Uptime: 2m55s (ada0:ata0:0:0:0): FLUSHCACHE. ACB: e7 00 00 00 00 40 00 00 00 00 00 00 (ada0:ata0:0:0:0): CAM status: Command timeout (ada0:ata0:0:0:0): Error 5, Retries exhausted (ada0:ata0:0:0:0): Synchronize cache failed Dumping 306 out of 4073 MB:(ada0:ata0:0:0:0): WRITE_DMA. ACB: ca 00 d8 6c 26 46 00 00 00 00 01 00 (ada0:ata0:0:0:0): CAM status: Command timeout (ada0:ata0:0:0:0): Error 5, Retries exhausted Aborting dump due to I/O error. ** DUMP FAILED (ERROR 5) ** ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
Re: VirtualBox 4.2.20_2 FreeBSD 9.2-RELEASE host multi CPU VM poudriere crash
2014/1/10 Derek Schrock der...@lifeofadishwasher.com: On Fri, Jan 10, 2014 at 05:18:24PM +0400, Mikhail Tsatsenko wrote: First of all attach serial console to VM and see if there is any kernel messages printed upon crash. Also there is a possibly similar problem: http://lists.freebsd.org/pipermail/freebsd-stable/2014-January/076772.html ___ FreeBSD/amd64 (freebsd10testing) (ttyu0) login: Jan 10 08:35:48 freebsd10testing su: dereks to root on /dev/pts/0 panic: handle_written_inodeblock: live inodedep 0xf80004eb1a00 cpuid = 0 KDB: stack backtrace: #0 0x808e7dd0 at kdb_backtrace+0x60 #1 0x808af8b5 at panic+0x155 #2 0x80ad3c85 at softdep_disk_write_complete+0x1595 #3 0x80934cb0 at bufdone_finish+0x30 #4 0x80934b18 at bufdone+0x78 #5 0x809346c2 at biodone+0xe2 #6 0x8081c561 at g_io_schedule_up+0x1b1 #7 0x8081ca5d at g_up_procbody+0x6d #8 0x8088198a at fork_exit+0x9a #9 0x80c758ce at fork_trampoline+0xe ok, that is completely different issue Uptime: 2m55s (ada0:ata0:0:0:0): FLUSHCACHE. ACB: e7 00 00 00 00 40 00 00 00 00 00 00 (ada0:ata0:0:0:0): CAM status: Command timeout (ada0:ata0:0:0:0): Error 5, Retries exhausted (ada0:ata0:0:0:0): Synchronize cache failed Dumping 306 out of 4073 MB:(ada0:ata0:0:0:0): WRITE_DMA. ACB: ca 00 d8 6c 26 46 00 00 00 00 01 00 (ada0:ata0:0:0:0): CAM status: Command timeout (ada0:ata0:0:0:0): Error 5, Retries exhausted Aborting dump due to I/O error. And that's why you can't get any dumps For some reason device disappears from guest machine. Did you check VirtualBox logs for something unusual? ** DUMP FAILED (ERROR 5) ** ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org -- Михаил ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
Re: VirtualBox 4.2.20_2 FreeBSD 9.2-RELEASE host multi CPU VM poudriere crash
On Fri, Jan 10, 2014 at 08:40:27AM -0500, Derek Schrock wrote: FreeBSD/amd64 (freebsd10testing) (ttyu0) login: Jan 10 08:35:48 freebsd10testing su: dereks to root on /dev/pts/0 panic: handle_written_inodeblock: live inodedep 0xf80004eb1a00 cpuid = 0 KDB: stack backtrace: #0 0x808e7dd0 at kdb_backtrace+0x60 #1 0x808af8b5 at panic+0x155 #2 0x80ad3c85 at softdep_disk_write_complete+0x1595 #3 0x80934cb0 at bufdone_finish+0x30 #4 0x80934b18 at bufdone+0x78 #5 0x809346c2 at biodone+0xe2 #6 0x8081c561 at g_io_schedule_up+0x1b1 #7 0x8081ca5d at g_up_procbody+0x6d #8 0x8088198a at fork_exit+0x9a #9 0x80c758ce at fork_trampoline+0xe Uptime: 2m55s (ada0:ata0:0:0:0): FLUSHCACHE. ACB: e7 00 00 00 00 40 00 00 00 00 00 00 (ada0:ata0:0:0:0): CAM status: Command timeout (ada0:ata0:0:0:0): Error 5, Retries exhausted (ada0:ata0:0:0:0): Synchronize cache failed Dumping 306 out of 4073 MB:(ada0:ata0:0:0:0): WRITE_DMA. ACB: ca 00 d8 6c 26 46 00 00 00 00 01 00 (ada0:ata0:0:0:0): CAM status: Command timeout (ada0:ata0:0:0:0): Error 5, Retries exhausted Aborting dump due to I/O error. ** DUMP FAILED (ERROR 5) ** Tried this again and got a totally different set of messages/backtrace. See the attached txt file. Fri Jan 10 08:41:58 EST 2014 FreeBSD/amd64 (freebsd10testing) (ttyu0) login: Jan 10 08:42:52 freebsd10testing su: dereks to root on /dev/pts/0 (ada0:ata0:0:0:0): WRITE_DMA. ACB: ca 00 22 18 56 41 00 00 00 00 00 00 (ada0:ata0:0:0:0): CAM status: Command timeout (ada0:ata0:0:0:0): Retrying command ada0 at ata0 bus 0 scbus0 target 0 lun 0 ada0: VBOX HARDDISK 1.0 s/n VB13c30ad6-e4c62d4b detached g_vfs_done():ada0p2[WRITE(offset=11478827008, length=131072)]error = 6 /: got error 6 while accessing filesystem /: got error 6 while accessing filesystem /: got error 6 while accessing filesystem /: got error 6 while accessing filesystem g_vfs_done():ada0p2[WRITE(offset=11478958080, length=131072)]error = 6 /: got error 6 while accessing filesystem /: got error 6 while accessing filesystem /: got error 6 while accessing filesystem /: got error 6 while accessing filesystem g_vfs_done():ada0p2[WRITE(offset=11479089152, length=131072)]error = 6 /: got error 6 while accessing filesystem /: got error 6 while accessing filesystem /: got error 6 while accessing filesystem /: got error 6 while accessing filesystem g_vfs_done():ada0p2[WRITE(offset=11479220224, length=131072)]error = 6 /: got error 6 while accessing filesystem /: got error 6 while accessing filesystem /: got error 6 while accessing filesystem /: got error 6 while accessing filesystem g_vfs_done():ada0p2[WRITE(offset=11479351296, length=131072)]error = 6 /: got error 6 while accessing filesystem /: got error 6 while accessing filesystem /: got error 6 while accessing filesystem /: got error 6 while accessing filesystem g_vfs_done():ada0p2[WRITE(offset=11479482368, length=131072)]error = 6 /: got error 6 while accessing filesystem /: got error 6 while accessing filesystem /: got error 6 while accessing filesystem /: got error 6 while accessing filesystem g_vfs_done():ada0p2[WRITE(offset=11479613440, length=131072)]error = 6 /: got error 6 while accessing filesystem /: got error 6 while accessing filesystem /: got error 6 while accessing filesystem /: got error 6 while accessing filesystem g_vfs_done():ada0p2[WRITE(offset=13432553472, length=98304)]error = 6 /: got error 6 while accessing filesystem /: got error 6 while accessing filesystem /: got error 6 while accessing filesystem g_vfs_done():ada0p2[WRITE(offset=13433241600, length=32768)]error = 6 /: got error 6 while accessing filesystem g_vfs_done():ada0p2[WRITE(offset=13384179712, length=8192)]error = 6 /: got error 6 while accessing filesystem g_vfs_done():ada0p2[WRITE(offset=13380444160, length=8192)]error = 6 /: got error 6 while accessing filesystem g_vfs_done():ada0p2[WRITE(offset=13385105408, length=32768)]error = 6 /: got error 6 while accessing filesystem g_vfs_done():ada0p2[WRITE(offset=13385203712, length=32768)]error = 6 /: got error 6 while accessing filesystem g_vfs_done():ada0p2[WRITE(offset=13374017536, length=12288)]error = 6 /: got error 6 while accessing filesystem g_vfs_done():ada0p2[WRITE(offset=13384548352, length=28672)]error = 6 /: got error 6 while accessing filesystem g_vfs_done():ada0p2[WRITE(offset=13384155136, length=24576)]error = 6 /: got error 6 while accessing filesystem g_vfs_done():ada0p2[WRITE(offset=13384089600, length=20480)]error = 6 /: got error 6 while accessing filesystem g_vfs_done():ada0p2[WRITE(offset=9879846912, length=16384)]error = 6 g_vfs_done():ada0p2[WRITE(offset=13431537664, length=98304)]error = 6 /: got error 6 while accessing filesystem /: got error 6 while accessing filesystem /: got error 6 while accessing filesystem g_vfs_done():ada0p2[WRITE(offset=13153562624, length=4096)]error = 6 /: got error 6 while accessing filesystem
