OpenVZ Forum: Support » [answered] VE on GFS/GFS2

Home » General » Support » [answered] VE on GFS/GFS2

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

[answered] VE on GFS/GFS2 [message #33783]

Mon, 10 November 2008 07:42

fbassas
Messages: 5
Registered: November 2008
Location: Terrassa (Barcelona)

Junior Member

(I posted following question in users forum, but perhaps here is the right place)
Hi,
we was running OpenVZ kernel 2.6.18-53.1.19.el5.028stab053.14 (on a Red Hat 5.2) and using GFS, and works quite good.

After migrating to 2.6.18-92.1.13.el5.028stab059.3 we noticed gfs module didn't work, and we saw that other users had the same
problem, and that the solution is to return to previous version.

We have set up a new server with this last OpenVZ version and GFS2, and although gfs2 module is load without problems, it seems
there are other issue related to gfs2 and devices access, getting the following message when trying to run a vzctl enter command:
"Unable to open pty: Invalid argument"
Also the problem has been confirmed by other users.

So, is there a prevision to solve this problems?
What is the right way at the moment? Old version with GFS? Will the gfs module work again in future releases?

Thanks in advance for your help

Frank
UPC - Terrassa - Spain

[Updated on: Mon, 10 November 2008 08:47] by Moderator

Report message to a moderator

Re: VE on GFS/GFS2 [message #33784 is a reply to message #33783]

Mon, 10 November 2008 07:59

khorenko
Messages: 533
Registered: January 2006
Location: Moscow, Russia

Senior Member

Hi Frank,

surely gfs will be fixed in future releases.
For now please, use older kernel with working gfs module or you can fix gfs in the current kernel by yourself and recompile the kernel.

The fix is extremely easy:

--- old/fs/gfs/proc.c	2008-10-24 12:52:30.000000000 +0400
+++ new/fs/gfs/proc.c	2008-10-24 12:53:43.000000000 +0400
@@ -474,7 +474,7 @@ gfs_proc_init(void)
 	spin_lock_init(&gfs_proc_margs_lock);
 	spin_lock_init(&gfs_req_lock);
 
-	pde = create_proc_entry("src/fs/gfs", S_IFREG | 0600, NULL);
+	pde = create_proc_entry("fs/gfs", S_IFREG | 0600, NULL);
 	if (!pde)
 		return -ENOMEM;
 
@@ -494,6 +494,6 @@ gfs_proc_uninit(void)
 {
 	if (gfs_proc_margs)
 		kfree(gfs_proc_margs);
-	remove_proc_entry("src/fs/gfs", NULL);
+	remove_proc_entry("fs/gfs", NULL);
 }

Hope this helps.

--
Konstantin

If your problem is solved - please, report it!
It's even more important than reporting the problem itself...

[Updated on: Mon, 10 November 2008 07:59]

Report message to a moderator

Re: VE on GFS/GFS2 [message #33786 is a reply to message #33784]

Mon, 10 November 2008 08:10

fbassas
Messages: 5
Registered: November 2008
Location: Terrassa (Barcelona)

Junior Member

OK regarding to gfs, what but about gfs2? are you aware of device files problems? Can that be solved in OpenVz point of view?

Regards.
Frank

Report message to a moderator

Re: VE on GFS/GFS2 [message #33788 is a reply to message #33786]

Mon, 10 November 2008 08:32

khorenko
Messages: 533
Registered: January 2006
Location: Moscow, Russia

Senior Member

Quote:

OK regarding to gfs, what but about gfs2? are you aware of device files problems?

Yes, we aware of it, we read forum. Smile

The workaround is here:
http://forum.openvz.org/index.php?t=msg&goto=31055&& amp;srch=gfs2#msg_31055

Quote:

Can that be solved in OpenVz point of view?

We do not recommend to use gfs2 as we found it unstable.
Surely the problem will be fixed some day, but i think it makes sense only after gfs2 become stable.

--
Konstantin

If your problem is solved - please, report it!
It's even more important than reporting the problem itself...

Report message to a moderator