Hello!
When "kernel.pid_ns_hide_child=1" sysctl flag is used, and one starts a new OpenVZ container it causes a crash into kernel panic on the latest and greatest "proxmox-ve-2.6.32: 3.4-166 (running kernel: 2.6.32-43-pve)". OpenVZ devs seem to know about the issue and will hopefully fix it...
Check the SMART attributes table of your drives (smartctl -a /dev/sdc) if attribute 190 is really the temperature attribute and if the reported values are really the temperature in (decimal) Celsius. (look at column RAW_VALUE)
Because, as you figured out yourself, a drive temperature of 69°C...
Do you use the enterprise or the no-subscription update channel?
Because on the latter channel I only have this quite old zfs/spl version "SPL: Loaded module v0.6.4-358_gaaf6ad2".
best regards
Hello,
You should post your kernel version and your zfs version.
As a pointer I am experiencing similar problems since an upgrade to kernel 2.6.32-40-pve and a newer zfs version
dmesg | grep -E 'SPL:|ZFS:'
SPL: Loaded module v0.6.4-358_gaaf6ad2
ZFS: Loaded module...
Hi!
I decided to post this here because serious problems too started after upgrade from 2.6.32-39-pve to the currently latest 2.6.32-40-pve.
After the upgrade the bi-weekly scrub of a zfs pool, which took approx. 3h started to take horribly long and resulted in the eventual crash of the...
Speaking of version mismatch, maybe is there a mismatch between SPL/ZFS versions in the current PVE version (kernel 2.6.32-40-pve)?
dmesg | grep -E 'SPL:|ZFS:'
SPL: Loaded module v0.6.4-358_gaaf6ad2
ZFS: Loaded module v0.6.4.1-1099_g7939064, ZFS pool version 5000, ZFS filesystem version 5...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.