[DragonFlyBSD - Bug #1298] (Closed) system hang due to hammer problem?

[bugtracker-admin at leaf.dragonflybsd.org]

Issue #1298 has been updated by tuxillo.

Description updated
Category set to VFS subsystem
Status changed from New to Closed
Assignee deleted (0)
Target version set to 4.2.x

Hi,

Old bug where we can't verify the issue. This could be caused by faulty disk drives (but not necessarily).
Closing it but feel free to reopen/open a new one if you can reproduce it.

Cheers,
Antonio Huete


----------------------------------------
Bug #1298: system hang due to hammer problem?
http://bugs.dragonflybsd.org/issues/1298#change-12446

* Author: pgeorgi
* Status: Closed
* Priority: Normal
* Assignee: 
* Category: VFS subsystem
* Target version: 4.2.x
----------------------------------------
This morning, my server was unresponsive (no network traffic, no console
response beyond switching terminals and entering ddb. Regular keypresses,
eg. at the login prompt weren't registered).
The last messages in the log were

Feb 25 03:05:23 t-stueck kernel: HAMMER(backup): Critical error
inode=24949148432 while syncing inode
Feb 25 03:05:23 t-stueck kernel: HAMMER(backup): Forcing read-only mode
Feb 25 03:05:29 t-stueck kernel: pid 532 (hammer), uid 0: exited on signal 11
(core dumped)

The HAMMER(backup) lines were also on the console.

I don't have a crash dump, and the hammer coredump isn't very useful either
(no binary with symbols around).
The system ran a "2.3.0-development" version from ~1 week ago or so. I think no
hammer related changes appeared since then.

The problem seems to have happened during a "hammer prune", as started by the
nightly "hammer cleanup", as the daily run mail reported:

cleanup /backup/root/home    - handle PFS #2 using /backup/pfs-snapshots/home
           snapshots - run
               prune - Segmentation fault (core dumped)

The security mail reported that PFS to be read-only, but it's not critical (it's
a pfs-slave to /home, on a different hammer partition than / and /home)



-- 
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