Issue #2819 has been updated by ftigeot.
The bug reporting tool sadly doesn't preserve whitespace.
The following lines are interesting and way out of line compared to other
values:
Type InUse MemUse HighUse Limit Requests Limit Limit
HAMMER-inodes 43004623762905K 0K 134203388K 35443885 0 0
vnodes 43027071747975K 0K 134203388K 35629122 0 0
vfscache 413619643672964K 0K 6498816K 1424298426 0 0
----------------------------------------
Bug #2819: Random micro system freezes after a week of uptime
http://bugs.dragonflybsd.org/issues/2819#change-12646
* Author: ftigeot
* Status: New
* Priority: Normal
* Assignee:
* Category:
* Target version:
----------------------------------------
On a file server, the system freeze for a few seconds to more than a minute
after aproximately a week of uptime.
The longer the machine stays up, the worse the freezes become. The
micro-freezes happen more often and become longer.
It is a complete kernel freeze: characters typed on the console stop appearing
on the screen when it happens.
Characters don't stop being displayed when the operating is stopped and the
kernel debugger is active, which indicates the problem is not of a hardware
origin.
Hardware specs:
- Xeon E5-2620, 64 GB RAM
- Areca RAID controller
- 2x 500GB system disks (RAID 1)
- 11x 2 GB data disks (RAID 5)
- 1x 512 GB SSD (JBOD), used entirely for swap
- 10Gb Intel X540 ethernet adapter
Software configuration:
- swapcache enabled, up to 85% of the available swap size
- deduplication enabled on the data volume
The data volume is used for two things:
- protein sequences
- a rsnapshot backup directory for various servers
--
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
