Bug#949505: NFS client nfs4_reclaim_open_state: unhandled error -521

2020-01-21 Thread Peter Viskup
Package: linux-image-amd64 Version: 4.19+105 During logrotation of files residing on NFS share the NFS client report error "nfs4_reclaim_open_state: unhandled error -521". After that all the listings of the directory were hanging on IO. Only the subdirectory is affected, files and other

Bug#908647: CPU hog during fcheck task

2018-09-12 Thread Peter Viskup
Package: linux-latest Version: 4.9.110-3+deb9u4 Severity: important After kernel update on Debian9 system from 4.9.65-3+deb9u1 to 4.9.110-3+deb9u4 the fcheck cron job run +45000 seconds instead of original +8500 seconds (tested twice with same results). Tested with command $ perf stat -B -o

Bug#693851: Xen domU dynamic memory extension not working

2012-11-28 Thread Peter Viskup
On 11/28/2012 12:24 AM, Peter Viskup wrote: Test if it is working for wheezy at least and let us know. I just found email [1] from Alexandre where he stated he tested the Wheezy version already and it is working. My issues with backported kernel could be related to hypervisor version 4.0

Bug#693851: Xen domU dynamic memory extension not working

2012-11-21 Thread Peter Viskup
On 11/21/2012 09:38 AM, Ian Campbell wrote: On Wed, 2012-11-21 at 00:32 +0100, Peter Viskup wrote: dom0 is booting linux-image-2.6.32-5-xen-amd64 and Debian's Xen 4.0.1 is installed on the system. There is long discussion [1] on the xen-users mailing list with no root cause found. I'm afraid

Bug#693851: Xen domU dynamic memory extension not working

2012-11-21 Thread Peter Viskup
On 11/21/2012 01:11 PM, Ben Hutchings wrote: On Wed, 2012-11-21 at 12:47 +0100, Peter Viskup wrote: On 11/21/2012 09:38 AM, Ian Campbell wrote: On Wed, 2012-11-21 at 00:32 +0100, Peter Viskup wrote: dom0 is booting linux-image-2.6.32-5-xen-amd64 and Debian's Xen 4.0.1 is installed

Bug#693851: Xen domU dynamic memory extension not working

2012-11-20 Thread Peter Viskup
outputs. [1] http://lists.xen.org/archives/html/xen-users/2012-11/msg00104.html Best regards, -- Peter Viskup (XEN) Xen version 4.0.1 (Debian 4.0.1-5.4) (ultrot...@debian.org) (gcc version 4.4.5 (Debian 4.4.5-8) ) Sat Sep 8 19:15:46 UTC 2012 (XEN) Bootloader: GRUB 1.98+20100804-14+squeeze1 (XEN

Bug#689861: Issues with Xen when all CPUs are available to dom0

2012-10-08 Thread Peter Viskup
regards, -- Peter Viskup -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/50733822.10...@gmail.com

Bug#689861: Issues with Xen when all CPUs are available to dom0

2012-10-07 Thread Peter Viskup
consider if it is related to kernel or not. Anyway - we just jump into situation where no dynamic domU's configuration change is possible and this is causing us serious manageability and serviceability issues. [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683170 Best regards, -- Peter

Bug#607114: Unresponsive Xen's dom0 system after 'general protection fault'

2012-02-18 Thread Peter Viskup
Hello Jonathan, unfortunately I upgraded that server to Squeeze already. The good news is that on Squeeze I already used xm block-attach many times without any issue. I have one last box with Lenny with some production systems, but cannot test that on this box. Best regards, -- Peter Viskup

Bug#607141: xm block-attach failed on domU

2011-01-09 Thread Peter Viskup
from VG named 'data' to my vhosts. -- Peter Viskup -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d2a392c.3030...@gmail.com

Bug#607114: Unresponsive Xen's dom0 system after 'general protection fault'

2010-12-14 Thread Peter Viskup
hangs. Looks like it has something to do with 8021q module. All Xen domU's with NATed networks are reachable. -- System Information: Debian Release: 5.0.7 -- Regards, Peter Viskup Dec 14 21:25:17 server2 kernel: [1480447.233563] general protection fault: [1] SMP Dec 14 21:25:17 server2

Bug#607114: Same error on second server

2010-12-14 Thread Peter Viskup
different on hardware - server1 is Xeon 3210 based with all Intel Ethernet cards - server2 is Opteron 2431 based with Broadcom Ethernet cards -- Peter Viskup Dec 5 23:10:31 server1 kernel: [350429.816318] BUG: unable to handle kernel paging request at 004817f0 Dec 5 23:10:31

Bug#607114: Unresponsive Xen's dom0 system after 'general protection fault'

2010-12-14 Thread Peter Viskup
to this backports kernel will help - just before I will install it. I am running production servers and cannot just test that. -- Peter Viskup -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive

Bug#607141: xm block-attach failed on domU

2010-12-14 Thread Peter Viskup
the domU from the pty (ssh) console. Both dom0 and domU were running same kernel version. -- Peter Viskup Dec 13 16:29:04 tis kernel: [83118.676876] BUG: unable to handle kernel NULL pointer dereference at Dec 13 16:29:04 tis kernel: [83118.676898] IP: [8038d104

Bug#607114: Unresponsive Xen's dom0 system after 'general protection fault'

2010-12-14 Thread Peter Viskup
On 12/15/2010 03:13 AM, Ben Hutchings wrote: Do you create or modify VLAN devices when creating a new domain? No I don't create nor modify VLAN interfaces. I just add them to the bridge named 'xenin'. My config is like this: # bond over cross-cabling auto bond1 iface bond1 inet static