[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-users] ERROR: -91 after Kernel Upgrade
Hi I don't believe this issue is Xen related in any way. Have you tried the OCFS2 users list? ocfs2-users@xxxxxxxxxxxxxx My bet is a kernel module mismatch between your servers because you have only changed one of the machines. Upgrading all of them *should* fix the issue logically but if it doesn't then post to the ocfs2-users list. Joseph. On 10 May 2011 21:52, Mike Fröhner <mikefroehner@xxxxxx> wrote: > Hey guys, > > I have a OCFS2 Cluster mounted at 4 xen-server (gentoo). Today I upgraded > the xen-kernel for tests at one server (server2) from 2.6.34-xen to > 2.6.38-xen-r1. After reboot the server couldn't mount the ocsfs2 device > anymore. > > ocfs2-tools version: sys-fs/ocfs2-tools-1.4.3 > > Modules are loaded and /config type configfs and /dlm type ocfs2_dlmfs are > mounted. > > server2 ~ # mount /data/ > mount.ocfs2: Protocol not available while mounting /dev/sdb1 on /data. Check > 'dmesg' for more information on this error. > > server2 ~ # dmesg > [ 802.267217] o2net: accepted connection from node server4 (num 3) at > 10.10.21.14:7777 > [ 802.871908] o2net: accepted connection from node server3 (num 2) at > 10.10.21.13:7777 > [ 805.295632] (mount.ocfs2,13964,2):dlm_send_nodeinfo:1233 ERROR: node > mismatch -92, node 2 > [ 805.295637] (mount.ocfs2,13964,2):dlm_try_to_join_domain:1616 ERROR: > status = -92 > [ 805.296322] (mount.ocfs2,13964,2):dlm_join_domain:1877 ERROR: status = > -92 > [ 805.296453] (mount.ocfs2,13964,2):dlm_register_domain:2143 ERROR: status > = -92 > [ 805.296453] (mount.ocfs2,13964,2):o2cb_cluster_connect:313 ERROR: status > = -92 > [ 805.296453] (mount.ocfs2,13964,2):ocfs2_dlm_init:3086 ERROR: status = -92 > [ 805.296504] (mount.ocfs2,13964,2):ocfs2_mount_volume:1899 ERROR: status = > -92 > [ 805.296504] ocfs2: Unmounting device (8,17) on (node 0) > [ 807.300027] o2net: no longer connected to node server3 (num 2) at > 10.10.21.13:7777 > [ 807.300074] o2net: no longer connected to node server4 (num 3) at > 10.10.21.14:7777 > > > Does anybody know this problem? Is this error caused by different kernel / > module versions? > > > Regards, > Mike > > > _______________________________________________ > Xen-users mailing list > Xen-users@xxxxxxxxxxxxxxxxxxx > http://lists.xensource.com/xen-users > -- Kind regards, Joseph. Founder | Director Orion Virtualisation Solutions | www.orionvm.com.au | Phone: 1300 56 99 52 | Mobile: 0428 754 846 _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |