[DragonFlyBSD - Bug #3056] (In Progress) HAMMER2 corruption - nonexistent files

bugtracker-admin at leaf.dragonflybsd.org bugtracker-admin at leaf.dragonflybsd.org
Sat Sep 16 11:06:55 PDT 2017

Issue #3056 has been updated by dillon.

Status changed from New to In Progress
Assignee set to dillon

I believe I fixed that one in the latest master with the sideq commit 7220df841c67.  It won't fix the existing disconnect between inode nlinks and directory entries but it should prevent new occurrences.  We have not yet confirmed that the fix actually prevents such things from happening, yet (testing now).

I will come up with a way to scrap the dead directory entries in an upcoming commit.  It might be possible to just unlink("path") already, but 'rm' won't do it because 'rm' calls access() and lstat() first (which need the inode to exist).


Bug #3056: HAMMER2 corruption - nonexistent files

* Author: arcade at b1t.name
* Status: In Progress
* Priority: Normal
* Assignee: dillon
* Category: Kernel
* Target version: 
After one crash (like a week ago) I got one dir damaged:

> find . | wc -l

> find . -type f |& wc -l

> find .

> find . -type f
find: ./standard/module.conf.9.cfg: No such file or directory
find: ./standard/module.music_control.7.cfg: No such file or directory
find: ./standard/module.everything-apps.3.cfg: No such file or directory
find: ./standard/module.ibar.7.cfg: No such file or directory
find: ./standard/module.syscon.6.cfg: No such file or directory

No messages on system console even with vfs.hammer2.debug=1. Not fixed with cleanup/blukfree. Current kernel: 2e8a93d8402e.

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