https://bugs.dragonflybsd.org/
https://bugs.dragonflybsd.org/favicon.ico?1629395208
2008-08-11T22:12:00Z
DragonFlyBSD bugtracker
DragonFlyBSD - Bug #1117: fsck coredumps under QEMU-KVM
https://bugs.dragonflybsd.org/issues/1117?journal_id=5222
2008-08-11T22:12:00Z
ahuete.devel
<ul></ul><p>I have noticed that the coredump only occurs if I interrupt the process <br />(by Ctrl+C):</p>
virtualdragon# ./fsck -f -y /dev/ad2s1a
<ul>
<li>/dev/ad2s1a</li>
<li>Last Mounted on /mnt/test</li>
<li>Phase 1 - Check Blocks and Sizes</li>
<li>Phase 2 - Check Pathnames</li>
<li>Phase 3 - Check Connectivity</li>
<li>Phase 4 - Check Reference Counts</li>
<li>Phase 5 - Check Cyl groups<br />3076 files, 56890 used, 136613 free (61 frags, 17069 blocks, 0.0% <br />fragmentation)<br />ad2: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=79<br />^Cad2: TIMEOUT - WRITE_DMA retrying (0 retries left) LBA=79<br />ad2: FAILURE - WRITE_DMA timed out LBA=79<br />fsck in free(): error: free_pages: pointer to wrong pageAbort (core dumped)<br />virtualdragon# Aug 11 16:45:30 virtualdragon kernel: pid 995 (fsck), uid <br />0: exit<br />ed on signal 6 (core dumped)</li>
</ul>
<p>Now I include a backtrace:</p>
<p>(gdb) bt<br />#0 0x080773ac in kill ()<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: lib/libcr/sys/ cleanup (Closed)" href="https://bugs.dragonflybsd.org/issues/1">#1</a> 0x0807509e in abort ()<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: K&R -> ANSI cleanup status (Closed)" href="https://bugs.dragonflybsd.org/issues/2">#2</a> 0x0805e611 in ?? ()<br /><a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: freebsds pipe-reverse test fails on dfly (Closed)" href="https://bugs.dragonflybsd.org/issues/3">#3</a> 0x0805e63b in ?? ()<br /><a class="issue tracker-1 status-5 priority-5 priority-high3 closed" title="Bug: Rework of nrelease (Closed)" href="https://bugs.dragonflybsd.org/issues/4">#4</a> 0x0805ef75 in ?? ()<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: sys/dev cleanup (Closed)" href="https://bugs.dragonflybsd.org/issues/5">#5</a> 0x0805f7ca in free ()<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: sys/emulation cleanup (Closed)" href="https://bugs.dragonflybsd.org/issues/6">#6</a> 0x08053ba3 in ckfini (markclean=0) at utilities.c:266<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: /sys/boot cleanup (Closed)" href="https://bugs.dragonflybsd.org/issues/7">#7</a> 0x08054701 in catch (sig=2) at utilities.c:487<br /><a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: make upgrade broken (Closed)" href="https://bugs.dragonflybsd.org/issues/8">#8</a> <signal handler called><br /><a class="issue tracker-1 status-5 priority-5 priority-high3 closed" title="Bug: panic with HEAD (Closed)" href="https://bugs.dragonflybsd.org/issues/9">#9</a> 0x08055e9c in write ()<br /><a class="issue tracker-1 status-5 priority-5 priority-high3 closed" title="Bug: make buildworld broken (Closed)" href="https://bugs.dragonflybsd.org/issues/10">#10</a> 0x08054009 in bwrite (fd=4, buf=0x28085000 "", blk=16, size=8192) at <br />utilities.c:350<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: libstand cleanup (Closed)" href="https://bugs.dragonflybsd.org/issues/11">#11</a> 0x08053996 in flush (fd=4, bp=0x808baa0) at utilities.c:226<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: /sys/net cleanup (Closed)" href="https://bugs.dragonflybsd.org/issues/12">#12</a> 0x08053c80 in ckfini (markclean=1) at utilities.c:281<br /><a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: Buildworld error/panic (Closed)" href="https://bugs.dragonflybsd.org/issues/13">#13</a> 0x0804c3b3 in checkfilesys (filesys=0xbfbff9b9 "/dev/ad2s1a", <br />mntpt=0x0, auxdata=0, child=0) at main.c:339<br /><a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: zombie processes waiting for a lock, smth to worry about? (Closed)" href="https://bugs.dragonflybsd.org/issues/14">#14</a> 0x0804bc1d in main (argc=0, argv=0xbfbff8d4) at main.c:148</p>
<p>Hope this helps a bit more.</p>
<p>Regards,<br />Antonio Huete</p>
DragonFlyBSD - Bug #1117: fsck coredumps under QEMU-KVM
https://bugs.dragonflybsd.org/issues/1117?journal_id=5281
2008-08-20T13:45:37Z
tuxillo
<ul></ul><p>There must be some kind of permission issue, because this problem goes away by<br />running QEMU-KVM as root</p>
DragonFlyBSD - Bug #1117: fsck coredumps under QEMU-KVM
https://bugs.dragonflybsd.org/issues/1117?journal_id=5282
2008-08-20T13:45:52Z
tuxillo
<ul></ul><p>This can be closed.</p>
DragonFlyBSD - Bug #1117: fsck coredumps under QEMU-KVM
https://bugs.dragonflybsd.org/issues/1117?journal_id=5327
2008-08-23T18:24:02Z
corecode
<ul></ul><p>What's the cause/solution?</p>
<p>cheers<br /> simon</p>
DragonFlyBSD - Bug #1117: fsck coredumps under QEMU-KVM
https://bugs.dragonflybsd.org/issues/1117?journal_id=5333
2008-08-27T01:38:04Z
tuxillo
<ul></ul><p>The problem was on the host (Linux) and not in the guest (DF). It seems that<br />although running QEMU-KVM with a user in kvm group, there are some problems<br />accessing the disk images (or something else). This is solved by running<br />QEMU-KVM as root.</p>