[DragonFlyBSD - Bug #3181] (Closed) mount_hammer2 panic on empty disks

bugtracker-admin at leaf.dragonflybsd.org bugtracker-admin at leaf.dragonflybsd.org
Tue Mar 19 21:45:45 PDT 2019

Issue #3181 has been updated by dillon.

Status changed from New to Closed
Assignee set to dillon

Reported panic fixed in both master and release branch.

The reported panic can occur if the root inode has been blown away by a partial clearing of the filesystem via dd, and then a mount is attempted.  H2 may still be able to find a valid volume header due to volume header redundancy, but the root inode is typically located at a low block number and is more easily destroyed.  The failure path was not handled properly and resulted in a panic.


Bug #3181: mount_hammer2 panic on empty disks

* Author: BJoe
* Status: Closed
* Priority: Normal
* Assignee: dillon
* Category: 
* Target version: Latest stable
This triggered a panic in VM (VirtualBox 5.2.16) on OSX 10.11.6:

mkdir /mnt
dd if=/dev/zero of=/dev/ad1
mount_hammer2 /dev/ad1 /mnt

hammer2_panic.png (32.9 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

More information about the Bugs mailing list