On Thu, Jul 29, 2010 at 11:41:45AM +0200, Oliver Heinz wrote: > Am Donnerstag, 29. Juli 2010 00:55:57 schrieb Herbert Poetzl: > > On Tue, Jul 27, 2010 at 10:46:28AM +0200, Oliver Heinz wrote: > > > Am Montag, 26. Juli 2010 23:50:53 schrieb Nirmal Guhan: > > > > I remember running into similar issue when I was running a kernel > > > > without vserver patch. Just wondering if that is the case for you too! > > > Kernel is Linux 2.6.32.16-grsec2.2.0-vs2.3.0.36.29.4 and Vserver > > > extensions are enabled (see vserver-info output below). Same issue > > > occurs with current Debian Squeeze/Sid Vserver enabled kernel. > > just try with 2.6.32.16 first, then if that works, with > > 2.6.32.16 + grsec, if that works too, try with > > 2.6.32.16 + Linux-VServer (no grsec) if that fails, > > we'll look into it :) > Trying to start a vserver with the plain kernel is challenging ;-) no need to start a guest, but usually, for testing purposes you can get away by simply using chroot ... > I found a little locking testsuite here > http://nfsv4.bullopensource.org/tools/tests/locktest.php > at it also complains about the missing lock function. > When using in non cluster mode (option localflocks) the testsuite is > successful. So it seems to be an GFS2 issue and I'll have to ask for > help on a different mailing list then. no problem, keep us updated ... best, Herbert > thanks so far, > Oliver > > > > > > TIA, > > Herbert > > > > > Oliver > > > > > > > --Nirmal > > > > > > > > On Mon, Jul 26, 2010 at 2:39 AM, Oliver Heinz <oheinz@fbihome.de> wrote: > > > > > Hi there, > > > > > > > > > > is there anybody running Vservers on GFS2? I can't find much about > > > > > the lockf() that it complains is not implemented. Not much about > > > > > fcntl-Problems with GFS either. GFS is running with > > > > > pacemaker/corosycn cluster stack. GFS2 was created with options "-p > > > > > lock_dlm -j2 -t pcmk:pcmk". I also to added them to the testfs.sh > > > > > (output below) > > > > > > > > > > I just tried and get: > > > > >> root@server-c:~# vserver -v testshared start > > > > >> secure-mount: lockf(): Function not implemented > > > > >> Failed to update mtab-file > > > > >> secure-mount: lockf(): Function not implemented > > > > >> Failed to update mtab-file > > > > >> secure-mount: lockf(): Function not implemented > > > > >> Failed to update mtab-file > > > > >> New network context is 40 > > > > >> Adding 192.168.5.40 192.168.7.40 > > > > >> New security context is 40 > > > > >> /etc/init.d/rc: line 74: /etc/default/rcS: No such file or directory > > > > >> error: '/etc/init.d/rc' exited outside the expected code flow. > > > > >> > > > > >> An error occured while executing the vserver startup sequence; when > > > > >> there are no other messages, it is very likely that the init-script > > > > >> (/etc/init.d/rc 3) failed. > > > > >> > > > > >> Common causes are: > > > > >> * /etc/rc.d/rc on Fedora Core 1 and RH9 fails always; the 'apt-rpm' > > > > >> build method knows how to deal with this, but on existing > > > > >> installations, appending 'true' to this file will help. > > > > >> > > > > >> > > > > >> Failed to start vserver 'testshared' > > > > > > > > > > Any Ideas? > > > > > > > > > > > > > > > > > > > > TIA, > > > > > Oliver > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > root@server-c:~# vserver-info > > > > > > > > > > Versions: > > > > > Kernel: 2.6.32.16-grsec2.2.0-vs2.3.0.36.29.4 > > > > > VS-API: 0x00020305 > > > > > > > > > > util-vserver: 0.30.215; Jun 18 2010, 13:35:17 > > > > > > > > > > Features: > > > > > CC: gcc, gcc (Debian 4.4.4-5) 4.4.4 > > > > > > > > > > CXX: g++, g++ (Debian 4.4.4-5) 4.4.4 > > > > > > > > > > CPPFLAGS: '' > > > > > > > > > > CFLAGS: '-Wall -g -O2 -std=c99 -Wall -pedantic -W > > > > > > > > > > -funit- at-a-time' > > > > > > > > > > CXXFLAGS: '-g -O2 -ansi -Wall -pedantic -W > > > > > > > > > > -fmessage-length=0 -funit-at-a-time' > > > > > > > > > > build/host: x86_64-pc-linux-gnu/x86_64-pc-linux-gnu > > > > > > > > > > Use dietlibc: yes > > > > > > > > > > Build C++ programs: yes > > > > > Build C99 programs: yes > > > > > > > > > > Available APIs: v13,net,v21,v22,v23,netv2 > > > > > > > > > > ext2fs Source: e2fsprogs > > > > > > > > > > syscall(2) invocation: alternative > > > > > > > > > > vserver(2) syscall#: 236/glibc > > > > > > > > > > crypto api: nss > > > > > > > > > > python bindings: no > > > > > > > > > > use library versioning: yes > > > > > > > > > > Paths: > > > > > prefix: /usr > > > > > > > > > > sysconf-Directory: /etc > > > > > > > > > > cfg-Directory: /etc/vservers > > > > > > > > > > initrd-Directory: $(sysconfdir)/init.d > > > > > > > > > > pkgstate-Directory: /var/run/vservers > > > > > > > > > > vserver-Rootdir: /var/lib/vservers > > > > > > > > > > root@server-c:~# ./testme.sh > > > > > Linux-VServer Test [V0.17] Copyright (C) 2003-2006 H.Poetzl > > > > > chcontext is working. > > > > > chbind is working. > > > > > Linux 2.6.32.16-grsec2.2.0-vs2.3.0.36.29.4 #1 SMP Tue Jul 13 10:55:57 > > > > > CEST 2010 x86_64 > > > > > Ea 0.30.215 236/glibc (DSa) <v13,net,v21,v22,v23,netv2> > > > > > VCI: 0002:0305 236 13000fb1 (TbsPHIW) > > > > > --- > > > > > [000]# succeeded. > > > > > [001]# succeeded. > > > > > [011]# succeeded. > > > > > [031]# succeeded. > > > > > [101]# succeeded. > > > > > [102]# succeeded. > > > > > [201]# succeeded. > > > > > [202]# succeeded. > > > > > > > > > > > > > > > > > > > > root@server-c:~# ./testfs.sh -t -D /dev/loop0 -F gfs2 -M /mnt > > > > > Linux-VServer FS Test [V0.23] Copyright (C) 2005-2009 H.Poetzl > > > > > Linux 2.6.32.16-grsec2.2.0-vs2.3.0.36.29.4 x86_64/0.30.215 > > > > > VCI: 0002:0305 236 13000fb1 (ID24) > > > > > --- > > > > > testing gfs2 filesystem ... > > > > > [000]. [001]* > >