[prev in list] [next in list] [prev in thread] [next in thread] 

List:       dragonfly-bugs
Subject:    [DragonFlyBSD - Bug #1933] (Closed) HAMMER Insufficient undo FIFO space panic
From:       bugtracker-admin () leaf ! dragonflybsd ! org
Date:       2021-12-29 10:47:27
Message-ID: redmine.journal-14233.20211229104727.256 () leaf ! dragonflybsd ! org
[Download RAW message or body]

Issue #1933 has been updated by mneumann.

Description updated
Status changed from New to Closed

Closing due to inactivity.

----------------------------------------
Bug #1933: HAMMER Insufficient undo FIFO space panic
http://bugs.dragonflybsd.org/issues/1933#change-14233

* Author: mneumann
* Status: Closed
* Priority: Normal
* Assignee: dillon
* Target version: 6.2
----------------------------------------
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/

---Files--------------------------------
hammer.tgz (63.7 KB)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
[prev in list] [next in list] [prev in thread] [next in thread]