System Crash report


  • LAYER 8

    second time in 2 days, what is it?

    textdump.tar.0
    info.0

    run lockinfo
    db:1:lockinfo> show locks
    No such command; use "help" to list available commands
    db:1:lockinfo>  show alllocks
    No such command; use "help" to list available commands
    db:1:lockinfo>  show lockedvnods
    Locked vnodes
    db:0:kdb.enter.default>  show pcpu
    cpuid        = 7
    dynamic pcpu = 0xfffffe01985f6380
    curthread    = 0xfffff80005260000: pid 28 "/ worker"
    curpcb       = 0xfffffe0000263cc0
    fpcurthread  = none
    idlethread   = 0xfffff80004985620: tid 100010 "idle: cpu7"
    curpmap      = 0xffffffff82b85998
    tssp         = 0xffffffff82bb6ae8
    commontssp   = 0xffffffff82bb6ae8
    rsp0         = 0xfffffe0000263cc0
    gs32p        = 0xffffffff82bbd340
    ldt          = 0xffffffff82bbd380
    tss          = 0xffffffff82bbd370
    db:0:kdb.enter.default>  bt
    Tracing pid 28 tid 100118 td 0xfffff80005260000
    kdb_enter() at kdb_enter+0x3b/frame 0xfffffe00002637a0
    vpanic() at vpanic+0x194/frame 0xfffffe0000263800
    panic() at panic+0x43/frame 0xfffffe0000263860
    ffs_blkfree_cg() at ffs_blkfree_cg+0x5e4/frame 0xfffffe0000263900
    ffs_blkfree() at ffs_blkfree+0x99/frame 0xfffffe0000263960
    indir_trunc() at indir_trunc+0x551/frame 0xfffffe0000263a50
    handle_workitem_freeblocks() at handle_workitem_freeblocks+0x24e/frame 0xfffffe0000263ab0
    process_worklist_item() at process_worklist_item+0x24a/frame 0xfffffe0000263b20
    softdep_process_worklist() at softdep_process_worklist+0xc2/frame 0xfffffe0000263b70
    softdep_flush() at softdep_flush+0x11f/frame 0xfffffe0000263bb0
    fork_exit() at fork_exit+0x83/frame 0xfffffe0000263bf0
    fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe0000263bf0
    --- trap 0, rip = 0, rsp = 0, rbp = 0 ---
    

    this is a VM virtualbox with 2.4.4-RELEASE-p3


  • Netgate Administrator

    Some file system issue: Panic String: ffs_blkfree_cg: freeing free block

    Old but likely still relevant:
    https://lists.freebsd.org/pipermail/freebsd-current/2011-October/028860.html

    Since that looks like VirtualBox it seems unlikely to be the actual drive so I would assume filesystem damage.

    Boot into single user mode and fsck it a few times.

    Steve


  • LAYER 8

    nope i run multiple time fsck until i saw file system clean
    problem persist, crash report and after a couple of hours the vm crash and i need to restart it,last time right 1 hours ago and now i'm out of office..
    happened 4/5 times this week.
    and every time i run fsck there are errors on suricata logs, maybe a combination of suricata/pfsense/virtualbox
    idk but i think i'm done with virtualbox.


  • Netgate Administrator

    Hmm, possibly actually a bad drive then or something odd in VBox.
    I run a few pfSense VMs in VBox here but not permenatntly on. I only use them for testing.

    Steve


  • LAYER 8

    uhm I should have warnings coming from my server if it was that, r710 poweredge with centos, dell manager say it's all ok on my raid.
    i will try qemu/kvm


Log in to reply