[issue1933] HAMMER Insufficient undo FIFO space panic

[Michael Neumann (via DragonFly issue tracker)]

New submission from Michael Neumann <mneumann at ntecs.de>:

Somehow my 120 GB HAMMER filesystem got into a situation where I couldn't
recover (mount r/w) anymore. Mounting it always failed with an "insufficient
undo FIFO space" panic. (See screenshots df-hammer{1-4}.png).

The only way to recover was to mount read-only and then copy to a new HAMMER
filesystem (see hammer-recovery-ro.png).

I tried with the most recent version of DragonFly (daily snapshot; i386), but
also with a 2.6 version.

Any thoughts why this could happen and what to do in this situation? It somehow
must have paniced the system while running for the first time, then paniced upon
reboot during HAMMER recovery.

Screenshots: http://leaf.dragonflybsd.org/~mneumann/hammer_insuff_fifo/

----------
assignedto: dillon
files: hammer.tgz
messages: 9412
nosy: dillon, mneumann
status: unread
title: HAMMER Insufficient undo FIFO space panic

_____________________________________________________
DragonFly issue tracker <bugs at lists.dragonflybsd.org>
<http://bugs.dragonflybsd.org/issue1933>
_____________________________________________________Attachment:
hammer.tgz
-------------- next part --------------
A non-text attachment was scrubbed...
Name: bin00000.bin
Type: application/octet-stream
Size: 65189 bytes
Desc: "Description: application/compressed-tar"
URL: <http://lists.dragonflybsd.org/pipermail/bugs/attachments/20101210/cafe9908/attachment-0021.bin>