Issue #1504 has been updated by tuxillo. Status changed from New to Closed
- There was a fix by Matt for related issues. - DMA errors that could indicate cable issues, if not problems in the drive itself. Closing this one. ---------------------------------------- Bug #1504: hammer crash on cleanups http://bugs.dragonflybsd.org/issues/1504#change-11839 * Author: corecode * Status: Closed * Priority: Normal * Assignee: tuxillo * Category: VFS subsystem * Target version: 3.8.0 ---------------------------------------- Redirecting to bugs@ Eugene wrote: > Hello All. > I've got a time-to-time reproducible panic while running cleanups on a > mirror built with hammer mirror-stream. > I'm running a system built on -DEVELOPMENT sources from August, 9th > (uses SILI device) and a following system layout: > > /dev/da0s1a / ufs rw 1 1 > /dev/da0s2b none swap sw 0 0 > /dev/da0s2h /HAMMER0 hammer rw 2 2 > /HAMMER0/pfs/var /var null rw 2 2 > /dev/da1s1a /mirror ufs rw 1 1 # not used > /dev/da1s2b none swap sw 0 0 > /dev/da1s2h /HAMMER1 hammer rw 2 2 > /HAMMER1/pfs/var /mirrorvar null rw 2 2 > proc /proc procfs rw 0 0 > > A kernel panic occurs on running daily cleanups on a slave part of > mirror and I managed to reproduce it manually while executing %hammer > reblock and %hammer rebalance commands on a slave pfs after a day or two > of uptime. > When running %hammer cleanup immediately after system boot-up, it always > runs fine and resumes with no error. > I've attached a screenshot of a latest panic I've got while running > cleanup. > > If there can be any solution for this problem? Which kernel version are you running? Please post a uname -a output. Also, please configure a dumpdev and capture a crash dump. cheers simon -- 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
