I upgraded the kernel on my proxmox servers to pve-kernel-2.6.32-19-pve today (previous running kernel was pve-kernel-2.6.32-11-pve).
Ever since I have problems mounting a ext4 filesystem image residing on a glusterfs share (glusterfs is a network file system based on fuse).
Whenever I try to mount the filesystem image, I get a kernel BUG at fs/fuse/file.c:1110! invalid opcode: 0000 [#1] SMP
If I boot the system with the old kernel, everything works fine.
The problem seems not to be limited to glusterfs but any file system that is based on fuse when using a recent OpenVZ kernel (see http://serverfault.com/questions/485874/centos-openvz-kernel-panic-when-mounting-ext4-truecrypt-volume-in-nokernelcrypto).
What could I do to find the source of the problem? For now, it's fine for me to run the old kernel, but it would be nice to have the problem fixed.
Ever since I have problems mounting a ext4 filesystem image residing on a glusterfs share (glusterfs is a network file system based on fuse).
Whenever I try to mount the filesystem image, I get a kernel BUG at fs/fuse/file.c:1110! invalid opcode: 0000 [#1] SMP
If I boot the system with the old kernel, everything works fine.
The problem seems not to be limited to glusterfs but any file system that is based on fuse when using a recent OpenVZ kernel (see http://serverfault.com/questions/485874/centos-openvz-kernel-panic-when-mounting-ext4-truecrypt-volume-in-nokernelcrypto).
What could I do to find the source of the problem? For now, it's fine for me to run the old kernel, but it would be nice to have the problem fixed.