Date: Tue, 02 Feb 2016 07:26:43 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 206836] Random Lockups of partition /var Message-ID: <bug-206836-8@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D206836 Bug ID: 206836 Summary: Random Lockups of partition /var Product: Base System Version: 10.2-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: schmidt@ze.tum.de CC: freebsd-amd64@FreeBSD.org CC: freebsd-amd64@FreeBSD.org I have 64 Servers Running on Supermicro blades. Most of them running 10.1-release. We are in the process of updating them to 10.2-release.=20 On all updated systems the /var partition locks after 20 to 50 days. Servic= es on the system start to fail. Login Block. On Preopen Connections I can acce= ss all other partitions just fine. Just accessing anything on /var blocks the whole process without return.=20 There are no massages on the console. We have to force power off to restart= the system.=20 All partitions where SU+Journaling. I've deactivated journaling on all partitions but the lockups are still coming.=20 On all systems are different services. (MySQL, Jenkins, Apache).=20 The same Hardware was working and still is working on 10.1-Release an earli= er releases just fine.=20 Hostname dd.mm.yyyy hh:mm Actions taken=20 ----------------------------------------------- amnesix 7. 9.2015 10:30 Reboot miraculix 29. 9.2015 03:00 Reboot amnesix 18.10.2015 05:00 Reboot amnesix 29.11.2015 16:00 Reboot. Disabled journaling olympia 12.12.2015 11:00 Reboot. Disabled journaling devzope 17.12.2015 04:00 Reboot. Disabled journaling miraculix 22.12.2015 01:20 Reboot. Disabled journaling olympia 30.12.2015 19:00 Reboot amnesix 9. 1.2016 02:00 Reboot. fsck -f on all partitions delphi 28. 1.2016 05:40 Reboot. Disabled journaling. fsck -f devzope 30. 1.2016 04:50 Reboot. fsck -f devzope 1. 2.2016 01:45 Reboot. fsck -f miraculix 2. 2.2016 06:30 Reboot. fsck -f The symptoms are always the same. After the Power down and reboot the Raid = is resyncing but the system is working just fine until the next lookup.=20 I've attached the dmesg.boot of one of the servers. They are all identical. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-206836-8>