Is there any downside staying with pve-kernel-4.10.17-5-pve kernel while 4.13 gets more stable ?
I wouldn't mind stability over features / performance / security.
Hi
Thank you for the updated kernel.
Downloaded and installed using apt-get install ./pve-kernel-4.10.17-5-pve_4.10.17-25_amd64.deb
I have updated my system with this new kernel 4.10.17-5 and zfs-zed once again WORKS PROPERLY , the 100% cpu usage is gone.
Also all the zfs commands works...
Hi
Thank you for the updated kernel.
Downloaded and installed using apt-get install ./pve-kernel-4.10.17-5-pve_4.10.17-25_amd64.deb
I have updated my system with this new kernel 4.10.17-5 and zfs-zed once again WORKS PROPERLY , the 100% cpu usage is gone.
Also all the zfs commands works...
Sorry for not replying for so long.
I will use this 4.10 kernel meanwhile.
I had loads of other issues and this had to be put on hold :)
But since it is pretty much important i will try and test with this.
Thanks a lot.
@fabian hi
yes i know but i have not had enough time to get to the bottom of this yet
and my system suffers, zfs send does not work anymore probably of this mixmatch, zfs-zed takes up 100% cpu on one core ...
this update was more like a "backgrade" for me
Don't mean to hijack your thread, but on my machine i had to disable zfs-zed due to eating up 100% cpu, 1 core maxed out.
But that might be cause im using old kernel ( couldn't get new one to give me a bootable system yet) + new zfs userland
I since noticed that the fix only fixes ones set of problems, where the error in syslog is abour root@pam having no email.
Now i can send mail to root and i get it on my forwarded address.
Yet ZFS-ZED send no mails, it used to work properly before the upgrade.
So i second that 0xFelix , it does...
Yes indeed, i would like to get to the bottom of this.
But as you can see I am not the only one with the problem.
I will have to make time and arrengments to test this weekend.
From now on i have to clone this system and upgrade first the test environment. But that needs extra hw, which i dont...
I understand, thanks.
The problem is i have no choice since the new kernel has problems with zfs import and gave me lvm2 error which i already disabled and was unable to issue zpool import , blkid and fdisk -l commands, it would all hang there doing nothing.
I am also geting an error with zpool events and zfs-zed 100% cpu usage.
root@pve1:~# zpool events
TIME CLASS
internal error: Bad file descriptor
Aborted
It is as described here :
https://github.com/zfsonlinux/zfs/issues/4720
root@pve1:~# dmesg | grep -i zfs
[...
I am also geting an error with zpool events and zfs-zed is using 100% cpu
root@pve1:~# zpool events
TIME CLASS
internal error: Bad file descriptor
Aborted
It is as described here :
https://github.com/zfsonlinux/zfs/issues/4720
root@pve1:~# dmesg | grep -i zfs
[...
Try this
https://forum.proxmox.com/threads/pve-5-mail-forward-failed-user-root-pam-does-not-have-a-email-address.35961/
Fixed my mail issues.
Mail was working fine prior to the latest upgrade, this fixed it.
Meanwhile i fixed my non-working email ... its a bug :
https://forum.proxmox.com/threads/pve-5-mail-forward-failed-user-root-pam-does-not-have-a-email-address.35961/
"this is a bug and will be fixed with the next update"
dcsapak, Jul 28, 2017
The fix is :
chmod g+s /usr/bin/pvemailforward...
Hi
Thanks for the reply.
I can not test now.
This is a production environment i can not test this now, maybe in the weekend.
Meanwhile i am using the old kernel which thank god works just fine.
But now email is broken also
Oct 25 10:44:30 pve1 postfix/qmgr[2691]: 37DCC1317A...
After a recent upgrade I also have issue booting and importing pools, blkid does not work neither, i opened a thread about it.
I've read about issue with grub not being able to load after zfs upgrade, so i did not upgrade my pool, thank god. So now it is using the old zfs/spl 0.6.5.
I was able...
Hi
I have a Proxmox system running latest proxmox with kernel 4.10.17-4-pve
I upgraded the system , it upgraded zfs also.
On the next reboot i was unable to boot into the system.
I got a lot of errors , tried a lot of fixes, nothing worked.
After somehow getting past "Waiting for udev to...
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.