Re: [Vserver] unify-dirs buglet?
On Tue, 09 Dec 2003 11:28, Roderick A. Anderson wrote;
> {/vservers.new}# unify-dirs -d ref tc
> unify-dirs: Unifying: ref tc
> unify-dirs: Processing ref...
> unify-dirs: Readdir OK
> unify-dirs: Processing tc...
> unify-dirs: Readdir OK
> unify-dirs: Processing ref/sbin...
> unify-dirs: Readdir OK
> unify-dirs: Processing tc/sbin...
> unify-dirs: Readdir OK
> unify-dirs: COMPARE: tc/sbin/install-info vs ref/sbin/install-info
> unify-dirs: digesting tc/sbin/install-info
> Error digesting tc/sbin/install-info; Input/output error at
> /root/bin/unify-dirs line 287.
Input/output error means that the OS returned EIO when a file was
read. As compared with EPERM (Permission Denied), this typically
means there was a hard error on the disk, or a bug in the VFS layer or
filesystem ( you're not running reiserfs perchance are you? ;) ).
This may manifest itself as a segfault if it was in the VFS layer. If
it's completely random, it might even mean that you have faulty RAM!
Does:
cat tc/sbin/install-info ref/sbin/install-info >/dev/null
Work?
If not, then you have a more serious problem. I'd look at the output
of `dmesg' to look for the IDE or SCSI layers complaining, or
otherwise take the system down to single and fsck the partition.
If it *does* work, but `unify-dirs' doesn't, then there is something
wierder going on - in which case, mail me /tmp/trace (off-list) from:
strace -fae -o /tmp/trace unify-dirs -d ref tc
--
Sam Vilain, [EMAIL PROTECTED]
The pursuit of truth and beauty is a sphere of activity in which we
are permitted to remain children all our lives.
ALBERT EINSTEIN
___
Vserver mailing list
[EMAIL PROTECTED]
http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] unify-dirs buglet?
On Mon, 8 Dec 2003, Sam Vilain wrote:
> On Sat, 06 Dec 2003 14:42, Roderick A. Anderson wrote;
> Running the script with -v or -d makes it a lot easier to debug.
> Could you run the script with -d and send me the output?
Still blows chunks.
{/vservers.new}# unify-dirs -d ref tc
unify-dirs: Unifying: ref tc
unify-dirs: Processing ref...
unify-dirs: Readdir OK
unify-dirs: Processing tc...
unify-dirs: Readdir OK
unify-dirs: Processing ref/sbin...
unify-dirs: Readdir OK
unify-dirs: Processing tc/sbin...
unify-dirs: Readdir OK
unify-dirs: COMPARE: tc/sbin/install-info vs ref/sbin/install-info
unify-dirs: digesting tc/sbin/install-info
Error digesting tc/sbin/install-info; Input/output error at
/root/bin/unify-dirs line 287.
{/vservers.new}# unify-dirs -v ref tc
unify-dirs: Unifying: ref tc
Error digesting tc/sbin/install-info; Input/output error at
/root/bin/unify-dirs line 287.
> Please also forward me the output of:
>
> perl -le 'eval"use $_",print"$_: ".${$_.::VERSION} foreach
> qw(Pod::Constants Class::Tangram Set::Object ReadDir);'
Attachment (check1.lst)
> and:
>
> perl -V
Attachment (check2.lst)
> If it segfaults, run it inside the debugger (ie perl -d unify-dirs -d
> ...) and just let it rip. Actually the best thing to do is to trap it
> with gdb and do a stack backtrace; get yourself a debug-perl and:
>
> gdb /usr/bin/debug-perl
> > b main
> > r -d /root/bin/unify-dirs -d
> PerlDB <1> c
> *segv*
> > bt
No joy and short on time right now. We're moving our equipment to our new
NOC tonight so I'm playing catch as catch can - still I wanted to provide
something sooner than later.
> If you make sure that the modules are built with debugging symbols,
> you can usually see clearly which module the bug is in... these sorts
> of bugs can be hard to track down otherwise.
A project for later this week unless your brilliance sees it sooner. :-)
Best,
Rod
--
"Open Source Software - You usually get more than you pay for..."
"Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL"
Summary of my perl5 (revision 5.0 version 8 subversion 0) configuration:
Platform:
osname=linux, osvers=2.4.18-11smp, archname=i386-linux-thread-multi
uname='linux daffy.perf.redhat.com 2.4.18-11smp #1 smp thu aug 15 06:41:59 edt
2002 i686 i686 i386 gnulinux '
config_args='-des -Doptimize=-O2 -march=i386 -mcpu=i686 -Dmyhostname=localhost
[EMAIL PROTECTED] -Dcc=gcc -Dcf_by=Red Hat, Inc. -Dinstallprefix=/usr -Dprefix=/usr
-Darchname=i386-linux -Dvendorprefix=/usr -Dsiteprefix=/usr -Duseshrplib -Dusethreads
-Duseithreads -Duselargefiles -Dd_dosuid -Dd_semctl_semun -Di_db -Ui_ndbm -Di_gdbm
-Di_shadow -Di_syslog -Dman3ext=3pm -Duseperlio -Dinstallusrbinperl -Ubincompat5005
-Uversiononly -Dpager=/usr/bin/less -isr'
hint=recommended, useposix=true, d_sigaction=define
usethreads=define use5005threads=undef useithreads=define usemultiplicity=define
useperlio=define d_sfio=undef uselargefiles=define usesocks=undef
use64bitint=undef use64bitall=undef uselongdouble=undef
usemymalloc=n, bincompat5005=undef
Compiler:
cc='gcc', ccflags ='-D_REENTRANT -D_GNU_SOURCE -fno-strict-aliasing
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I/usr/include/gdbm',
optimize='-O2 -march=i386 -mcpu=i686',
cppflags='-D_REENTRANT -D_GNU_SOURCE -fno-strict-aliasing -I/usr/include/gdbm'
ccversion='', gccversion='3.2 20020822 (Red Hat Linux Rawhide 3.2-5)',
gccosandvers=''
intsize=4, longsize=4, ptrsize=4, doublesize=8, byteorder=1234
d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=12
ivtype='long', ivsize=4, nvtype='double', nvsize=8, Off_t='off_t', lseeksize=8
alignbytes=4, prototype=define
Linker and Libraries:
ld='gcc', ldflags =' -L/usr/local/lib'
libpth=/usr/local/lib /lib /usr/lib
libs=-lnsl -lgdbm -ldb -ldl -lm -lpthread -lc -lcrypt -lutil
perllibs=-lnsl -ldl -lm -lpthread -lc -lcrypt -lutil
libc=/lib/libc-2.2.92.so, so=so, useshrplib=true, libperl=libperl.so
gnulibc_version='2.2.92'
Dynamic Linking:
dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags='-rdynamic
-Wl,-rpath,/usr/lib/perl5/5.8.0/i386-linux-thread-multi/CORE'
cccdlflags='-fpic', lddlflags='-shared -L/usr/local/lib'
Characteristics of this binary (from libperl):
Compile-time options: MULTIPLICITY USE_ITHREADS USE_LARGE_FILES PERL_IMPLICIT_CONTEXT
Built under linux
Compiled at Sep 1 2002 23:56:49
@INC:
/usr/lib/perl5/5.8.0/i386-linux-thread-multi
/usr/lib/perl5/5.8.0
/usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi
/usr/lib/perl5/site_perl/5.8.0
/usr/lib/perl5/site_perl
/usr/lib/perl5/vendor_perl/5.8.0/i386-linux-thread-multi
/usr/lib/perl5/vendor_perl/5.8.0
/usr/lib/perl5/vendor_perl
.
Pod::Constants: 0.15
Class::Tangram:
Set::Object:
ReadDir: 0.02
Re: [Vserver] fcntl on NFS still broken on vs1.20
On Mon, Dec 08, 2003 at 01:22:46PM +0100, Jan Zuchhold wrote: > 2.4.22ctx-17c: works, no problem > 2.4.22-vs1.00: does not work, fcntl broken > 2.4.23-vs1.20: does not work, fcntl broken okay, we have to do some testing, as I announced before ... http://vserver.13thfloor.at/Stuff/patch-net01-2.4.22-ctx17c-vs1.00.diff this patch should be applied to 2.4.22ctx-17c with # patch -p1 <../patch-net01-2.4.22-ctx17c-vs1.00.diff and to 2.4.22-vs1.00 with # patch -R -p1 <../patch-net01-2.4.22-ctx17c-vs1.00.diff resulting in two kernels, one called linux-2.4.22ctx-17c-net01 and the other linux-2.4.22-vs1.00-net01r there should be _no_ warning or error in the process of patching both kernels, otherwise we have different kernels (which would be interesting) now I would like you to check both kernels with the same .config file and do the following (to compile) # make mrproper # cp ../TEST.config .config # make oldconfig # make dep >../Dep.log # make bzImage modules >../Build.log install and test ... TIA, Herbert PS: didn't find a difference, and unfortunately could not reproduce yet ... ___ Vserver mailing list [EMAIL PROTECTED] http://list.linux-vserver.org/mailman/listinfo/vserver
[Vserver] How to stabilize VServer Environment
On Mon, Dec 08, 2003 at 08:04:54AM -0500, [EMAIL PROTECTED] wrote: > Hello Herbert, > > I'm I so confused on where I need to start, I have a a > completely new install of RH9 w/ kernel 2.4.20-6. currently Alex's FreeVPS is the only version supporting 2.4.x RH kernels, I'm not sure if 2.4.20-6 is supported yet ... > I want to get as close to stable as possible, also I would > like to say that I'm learning much from the vserver community, > and everyone committed to the project, my applause you all great, guess you are now part of that community ;) > If someone can point me in the direction to stabilizing an > environment for vserver web hosting w/ a control panel like > (Plesk or Ensim, ect), I would very much appreciate it. don't know about frontends or control panels, there are some projects working on that, and you might find some links on the site wiki ... (anybody with good suggestions, speak up!) > p.s. If I need to upgrade the kernel, what procedures will I > need to follow to do this? I've never patched a kernel by hand > before, and I've alway just ran the rpm's to do this. the process of kernel patching/building, basically boils down to the following sequence: 1) download kernel sources and patches ... # tar xjf linux-2.4.23.tar.bz2 # wget http://www.13thfloor.at/vserver/s_release/v1.20/patch-2.4.23-vs1.20.diff 2) patch the kernel # cd linux-2.4.23 # patch -p1 <../patch-2.4.23-vs1.20.diff 3) copy the 'old' kernel config of your current kernel # cp ~/kernel.config .config 4) configure the kernel (only new options are asked) # make oldconfig # make menuconfig 5) build the dependancies and the kernel/modules # make dep >../Dep.log # make bzImage modules >../Build.log 6) install the resulting kernel and modules # make install modules_install 7) configure/check the bootloader lilo/grub/whatever > I currently have FreeVPS running and it great, thanks ALEX, > and your documentation is perfect. I just want to offer the > latest RH OS to customers.. while Alex's branch is more RH specific, you can use a vanill kernel with vs1.00/vs1.20 on the host system as there should be no issues with RH OS on a vanilla kernel, YMMV best, Herbert > Thank you. > TyroneM > ___ Vserver mailing list [EMAIL PROTECTED] http://list.linux-vserver.org/mailman/listinfo/vserver
Re: Re[2]: [Vserver] Stable vs1.20 + grsecurity + ippersonality
On Mon, Dec 08, 2003 at 11:42:56AM +0100, Michael Pasdziernik wrote: > hi alex, > > there is a link for a patch vserver+grsecurity on the linux-vserver.org website: > > http://www.firehead.org/~jeffrey/linux-vserver/ > > did you know that? have you tried that? Is this a new link? I just upgraded my 2.4.21-ctx17 devel machine to 2.4.23-ow1-vs1.20. ow1 is http://www.openwall.com/linux/linux-2.4.23-ow1.tar.gz. This patch gives me most of the (for me) interesting parts from grsec and applies cleanly together with vserver so I don't have to hack any source. The machine has been running for 6 hours now with users working on it and I haven't seen any unexpected sideeffects yet, so it looks stable to me. Regards, Erik Smit ___ Vserver mailing list [EMAIL PROTECTED] http://list.linux-vserver.org/mailman/listinfo/vserver
RE: [vserver] Copying vservers
On Mon, 8 Dec 2003, Mark Lawrence wrote:
> I fixed the ownership problem some time ago. I even posted the code to the
> list and/or the tool maintainers but I guess it got lost... Perhaps
> Roderick can tell us where he obtained the script from?
The Wiki Page.
http://vserver.strahlungsfrei.de/tiki-index.php?page=CopyVServers
> I have attached my latest copy plus the *man* page which gives an example
> of how to copy from one host to another. As others have pointed out there
> are other ways to do it manually, however I suggest that to make life easy
> for newcomers it is worth having a documented tool.
Thanks. I'll take a further look.
Rod
--
"Open Source Software - You usually get more than you pay for..."
"Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL"
___
Vserver mailing list
[EMAIL PROTECTED]
http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] fcntl on NFS still broken on vs1.20
On Mon, Dec 08, 2003 at 01:22:46PM +0100, Jan Zuchhold wrote: > > > I just tested vs1.20 and it appears that fcntl locking on NFS shares > > > mounted inside a vserver is still broken, as I reported some time ago > > > (04.11.2003). I quote from my other posts: > > 2.4.22ctx-17c: works, no problem > 2.4.22-vs1.00: does not work, fcntl broken > 2.4.23-vs1.20: does not work, fcntl broken > > > hmm, so this _is_ working with 2.4.22ctx-17c? > > yep, i just checked, i used exactly the same config > for 2.4.22-vs1.00 and 2.4.22ctx-17c. > > > there should be no difference in behaviour between > > 2.4.22ctx-17c and vs1.00 ... > > Well, maybe it should, but it isn't ;) hey, I consider that lucky, because we just have to look at the differences between vs1.00 and ctx-17c to locate _and_ fix this ;) I'll look for it, and make some simple patches, to test ... maybe you can pay a visit on the irc channel? TIA, Herbert > ___ > Vserver mailing list > [EMAIL PROTECTED] > http://list.linux-vserver.org/mailman/listinfo/vserver ___ Vserver mailing list [EMAIL PROTECTED] http://list.linux-vserver.org/mailman/listinfo/vserver
Re[4]: [Vserver] Stable vs1.20 + grsecurity + ippersonality
Hello Michael, Monday, December 8, 2003, 5:42:56 AM, you wrote: MP> hi alex, MP> there is a link for a patch vserver+grsecurity on the linux-vserver.org website: MP> http://www.firehead.org/~jeffrey/linux-vserver/ MP> did you know that? have you tried that? Is this a new link? Nope , haven't heard of that. Still the difference is that I'm doing swsusp+grsecurity+vserver, not just grsecurity+vserver. However swsusp can use some extra #ifdef's because if you disable it bad things start happening. -- Alexmailto:[EMAIL PROTECTED] 10:35:10 AM Monday, December 8, 2003 EDT ___ Vserver mailing list [EMAIL PROTECTED] http://list.linux-vserver.org/mailman/listinfo/vserver
Re: Re: [Vserver] fcntl on NFS still broken on vs1.20
Hello Herbert,
I'm I so confused on where I need to start, I have a a completely new install
of RH9 w/ kernel 2.4.20-6. I want to get as close to stable as possible, also I would
like to say that I'm learning much from the vserver community, and everyone committed
to the project, my applause you all
If someone can point me in the direction to stabilizing an environment for vserver web
hosting w/ a control panel like (Plesk or Ensim, ect), I would very much appreciate it.
p.s. If I need to upgrade the kernel, what procedures will I need to follow to do
this? I've never patched a kernel by hand before, and I've alway just ran the rpm's to
do this.
I currently have FreeVPS running and it great, thanks ALEX, and your documentation is
perfect. I just want to offer the latest RH OS to customers..
Thank you.
TyroneM
>
> From: Herbert Poetzl <[EMAIL PROTECTED]>
> Date: 2003/12/08 Mon AM 07:02:44 EST
> To: Jan Zuchhold <[EMAIL PROTECTED]>
> CC: [EMAIL PROTECTED]
> Subject: Re: [Vserver] fcntl on NFS still broken on vs1.20
>
> On Mon, Dec 08, 2003 at 12:29:31PM +0100, Jan Zuchhold wrote:
> > Hello List!
>
> Hi Jan!
>
> > I just tested vs1.20 and it appears that fcntl locking on NFS shares mounted
> > inside a vserver is still broken, as I reported some time ago (04.11.2003). I
> > quote from my other posts:
> >
> > The share is mounted like this in the vserver startup script:
> >
> > /usr/sbin/chbind --ip 192.168.1.145 --bcast 192.168.1.255 mount -t nfs
> > fileserver:/home /var/lib/vservers/$2/home
> >
> > Script to reproduce error:
> >
> >
> > #!/usr/bin/perl
> >
> > use Fcntl;
> >
> > open FH, ">locktest.lock" or die "Cannot open $fn: $!";
> > print "Testing fcntl...\n";
> > @list = (F_WRLCK,0,0,0,0); # exclusive write lock, entire file
> > $struct = pack("SSLLL",@list);
> > fcntl(FH,&F_SETLKW,$struct) or die("cannot lock because: $!\n");
> >
> > # With vs1.00 and vs1.20 I don't get here
> >
> > print FH "blabla";
> >
> > close FH;
> >
> >
> > Symptoms: NFS Share stops responding, all processes go to state D.
> >
> > Because of this problem nearly all of my machines are stuck at 2.4.22ctx-17c.
>
> hmm, so this _is_ working with 2.4.22ctx-17c?
>
> which patch of vs1.20 did you try, the one for 2.4.22
> and the 2.4.22 source or the one for 2.4.23?
>
> did you use the _same_ config file as for the
> 2.4.22ctx-17c?
>
> did 2.4.22-vs1.00 work for you?
>
>
> > Is there anything I can do to get this bug fixed?
>
> if you used the 2.4.23, could you try with 2.4.22+patch
> and if this works, 2.4.23 without patch?
>
> could you try 2.4.22-vs1.00 with the same config as
> 2.4.22ctx-17c, and see if it works?
>
> I will try to reproduce ...
> there should be no difference in behaviour between
> 2.4.22ctx-17c and vs1.00 ...
>
> TIA,
> Herbert
>
> > Thank you,
> > Jan
> >
> > ___
> > Vserver mailing list
> > [EMAIL PROTECTED]
> > http://list.linux-vserver.org/mailman/listinfo/vserver
> ___
> Vserver mailing list
> [EMAIL PROTECTED]
> http://list.linux-vserver.org/mailman/listinfo/vserver
>
___
Vserver mailing list
[EMAIL PROTECTED]
http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] fcntl on NFS still broken on vs1.20
> > I just tested vs1.20 and it appears that fcntl locking on NFS shares
> > mounted inside a vserver is still broken, as I reported some time ago
> > (04.11.2003). I quote from my other posts:
> >
> > The share is mounted like this in the vserver startup script:
> >
> > /usr/sbin/chbind --ip 192.168.1.145 --bcast 192.168.1.255 mount -t nfs
> > fileserver:/home /var/lib/vservers/$2/home
> >
> > Script to reproduce error:
> >
> >
> > #!/usr/bin/perl
> >
> > use Fcntl;
> >
> > open FH, ">locktest.lock" or die "Cannot open $fn: $!";
> > print "Testing fcntl...\n";
> > @list = (F_WRLCK,0,0,0,0); # exclusive write lock, entire file
> > $struct = pack("SSLLL",@list);
> > fcntl(FH,&F_SETLKW,$struct) or die("cannot lock because: $!\n");
> >
> > # With vs1.00 and vs1.20 I don't get here
> >
> > print FH "blabla";
> >
> > close FH;
> >
> >
> > Symptoms: NFS Share stops responding, all processes go to state D.
> >
> > Because of this problem nearly all of my machines are stuck at
> > 2.4.22ctx-17c.
2.4.22ctx-17c: works, no problem
2.4.22-vs1.00: does not work, fcntl broken
2.4.23-vs1.20: does not work, fcntl broken
> hmm, so this _is_ working with 2.4.22ctx-17c?
yep
> which patch of vs1.20 did you try, the one for 2.4.22
> and the 2.4.22 source or the one for 2.4.23?
> did you use the _same_ config file as for the
> 2.4.22ctx-17c?
yep, i just checked, i used exactly the same config for 2.4.22-vs1.00 and
2.4.22ctx-17c.
> I will try to reproduce ...
> there should be no difference in behaviour between
> 2.4.22ctx-17c and vs1.00 ...
Well, maybe it should, but it isn't ;)
___
Vserver mailing list
[EMAIL PROTECTED]
http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] fcntl on NFS still broken on vs1.20
On Monday 08 December 2003 14:16, you wrote: > On Mon, Dec 08, 2003 at 02:06:50PM +0200, Alex Lyashkov wrote: > > On Monday 08 December 2003 13:29, Jan Zuchhold wrote: > > > Hello List! > > > > > > I just tested vs1.20 and it appears that fcntl locking on NFS shares > > > mounted inside a vserver is still broken, as I reported some time ago > > > (04.11.2003). I quote from my other posts: > > [ script and explanation removed ] > > > At testlab run this test script and not found this bug in freevps-1.1.0. > > == > > [EMAIL PROTECTED] root]# ./testnfs.pl > > Testing fcntl... > > [EMAIL PROTECTED] root]# > > cat locktest.lock > > [EMAIL PROTECTED] root]# > > === > > after it share work correctly - dir can been changed and files been read. > > > > for test share do mounting inside vps. > > well, it wasn't very likely that your branch > would have this issues, (if it's a vserver issue > anyway) because your codebase branched long > before the ctx-17c, which seems to work ... but if bug in nfs code RH kernels can be affected this bug. I test only it. -- With best regards, Alex ___ Vserver mailing list [EMAIL PROTECTED] http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] fcntl on NFS still broken on vs1.20
On Mon, Dec 08, 2003 at 02:06:50PM +0200, Alex Lyashkov wrote: > On Monday 08 December 2003 13:29, Jan Zuchhold wrote: > > Hello List! > > > > I just tested vs1.20 and it appears that fcntl locking on NFS shares > > mounted inside a vserver is still broken, as I reported some time ago > > (04.11.2003). I quote from my other posts: [ script and explanation removed ] > At testlab run this test script and not found this bug in freevps-1.1.0. > == > [EMAIL PROTECTED] root]# ./testnfs.pl > Testing fcntl... > [EMAIL PROTECTED] root]# > cat locktest.lock > [EMAIL PROTECTED] root]# > === > after it share work correctly - dir can been changed and files been read. > > for test share do mounting inside vps. well, it wasn't very likely that your branch would have this issues, (if it's a vserver issue anyway) because your codebase branched long before the ctx-17c, which seems to work ... best, Herbert > -- > With best regards, > Alex > ___ > Vserver mailing list > [EMAIL PROTECTED] > http://list.linux-vserver.org/mailman/listinfo/vserver ___ Vserver mailing list [EMAIL PROTECTED] http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] fcntl on NFS still broken on vs1.20
On Monday 08 December 2003 13:29, Jan Zuchhold wrote:
> Hello List!
>
> I just tested vs1.20 and it appears that fcntl locking on NFS shares
> mounted inside a vserver is still broken, as I reported some time ago
> (04.11.2003). I quote from my other posts:
>
> The share is mounted like this in the vserver startup script:
>
> /usr/sbin/chbind --ip 192.168.1.145 --bcast 192.168.1.255 mount -t nfs
> fileserver:/home /var/lib/vservers/$2/home
>
> Script to reproduce error:
>
>
> #!/usr/bin/perl
>
> use Fcntl;
>
> open FH, ">locktest.lock" or die "Cannot open $fn: $!";
> print "Testing fcntl...\n";
> @list = (F_WRLCK,0,0,0,0); # exclusive write lock, entire file
> $struct = pack("SSLLL",@list);
> fcntl(FH,&F_SETLKW,$struct) or die("cannot lock because: $!\n");
>
> # With vs1.00 and vs1.20 I don't get here
>
> print FH "blabla";
>
> close FH;
>
>
> Symptoms: NFS Share stops responding, all processes go to state D.
>
> Because of this problem nearly all of my machines are stuck at
> 2.4.22ctx-17c.
>
> Is there anything I can do to get this bug fixed?
>
At testlab run this test script and not found this bug in freevps-1.1.0.
==
[EMAIL PROTECTED] root]# ./testnfs.pl
Testing fcntl...
[EMAIL PROTECTED] root]#
cat locktest.lock
[EMAIL PROTECTED] root]#
===
after it share work correctly - dir can been changed and files been read.
for test share do mounting inside vps.
--
With best regards,
Alex
___
Vserver mailing list
[EMAIL PROTECTED]
http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] fcntl on NFS still broken on vs1.20
On Mon, Dec 08, 2003 at 12:29:31PM +0100, Jan Zuchhold wrote:
> Hello List!
Hi Jan!
> I just tested vs1.20 and it appears that fcntl locking on NFS shares mounted
> inside a vserver is still broken, as I reported some time ago (04.11.2003). I
> quote from my other posts:
>
> The share is mounted like this in the vserver startup script:
>
> /usr/sbin/chbind --ip 192.168.1.145 --bcast 192.168.1.255 mount -t nfs
> fileserver:/home /var/lib/vservers/$2/home
>
> Script to reproduce error:
>
>
> #!/usr/bin/perl
>
> use Fcntl;
>
> open FH, ">locktest.lock" or die "Cannot open $fn: $!";
> print "Testing fcntl...\n";
> @list = (F_WRLCK,0,0,0,0); # exclusive write lock, entire file
> $struct = pack("SSLLL",@list);
> fcntl(FH,&F_SETLKW,$struct) or die("cannot lock because: $!\n");
>
> # With vs1.00 and vs1.20 I don't get here
>
> print FH "blabla";
>
> close FH;
>
>
> Symptoms: NFS Share stops responding, all processes go to state D.
>
> Because of this problem nearly all of my machines are stuck at 2.4.22ctx-17c.
hmm, so this _is_ working with 2.4.22ctx-17c?
which patch of vs1.20 did you try, the one for 2.4.22
and the 2.4.22 source or the one for 2.4.23?
did you use the _same_ config file as for the
2.4.22ctx-17c?
did 2.4.22-vs1.00 work for you?
> Is there anything I can do to get this bug fixed?
if you used the 2.4.23, could you try with 2.4.22+patch
and if this works, 2.4.23 without patch?
could you try 2.4.22-vs1.00 with the same config as
2.4.22ctx-17c, and see if it works?
I will try to reproduce ...
there should be no difference in behaviour between
2.4.22ctx-17c and vs1.00 ...
TIA,
Herbert
> Thank you,
> Jan
>
> ___
> Vserver mailing list
> [EMAIL PROTECTED]
> http://list.linux-vserver.org/mailman/listinfo/vserver
___
Vserver mailing list
[EMAIL PROTECTED]
http://list.linux-vserver.org/mailman/listinfo/vserver
[Vserver] fcntl on NFS still broken on vs1.20
Hello List!
I just tested vs1.20 and it appears that fcntl locking on NFS shares mounted
inside a vserver is still broken, as I reported some time ago (04.11.2003). I
quote from my other posts:
The share is mounted like this in the vserver startup script:
/usr/sbin/chbind --ip 192.168.1.145 --bcast 192.168.1.255 mount -t nfs
fileserver:/home /var/lib/vservers/$2/home
Script to reproduce error:
#!/usr/bin/perl
use Fcntl;
open FH, ">locktest.lock" or die "Cannot open $fn: $!";
print "Testing fcntl...\n";
@list = (F_WRLCK,0,0,0,0); # exclusive write lock, entire file
$struct = pack("SSLLL",@list);
fcntl(FH,&F_SETLKW,$struct) or die("cannot lock because: $!\n");
# With vs1.00 and vs1.20 I don't get here
print FH "blabla";
close FH;
Symptoms: NFS Share stops responding, all processes go to state D.
Because of this problem nearly all of my machines are stuck at 2.4.22ctx-17c.
Is there anything I can do to get this bug fixed?
Thank you,
Jan
___
Vserver mailing list
[EMAIL PROTECTED]
http://list.linux-vserver.org/mailman/listinfo/vserver
Re: Re[2]: [Vserver] Stable vs1.20 + grsecurity + ippersonality
hi alex, there is a link for a patch vserver+grsecurity on the linux-vserver.org website: http://www.firehead.org/~jeffrey/linux-vserver/ did you know that? have you tried that? Is this a new link? ciao Michael __ Horoskop, Comics, VIPs, Wetter, Sport und Lotto im WEB.DE Screensaver1.2 Kostenlos downloaden: http://screensaver.web.de/?mc=021110 ___ Vserver mailing list [EMAIL PROTECTED] http://list.linux-vserver.org/mailman/listinfo/vserver
Re: Re[2]: [Vserver] Stable vs1.20 + grsecurity + ippersonality
hi alex, there is a link for a patch vserver+grsecurity on the linux-vserver.org website: http://www.firehead.org/~jeffrey/linux-vserver/ did you know that? have you tried that? Is this a new link? ciao Michael __ WEB.DE FreeMail wird 5 Jahre jung! Feiern Sie mit uns und nutzen Sie die neuen Funktionen http://f.web.de/features/?mc=021130 ___ Vserver mailing list [EMAIL PROTECTED] http://list.linux-vserver.org/mailman/listinfo/vserver
RE: [vserver] Copying vservers
I fixed the ownership problem some time ago. I even posted the code to the
list and/or the tool maintainers but I guess it got lost... Perhaps
Roderick can tell us where he obtained the script from?
I have attached my latest copy plus the *man* page which gives an example
of how to copy from one host to another. As others have pointed out there
are other ways to do it manually, however I suggest that to make life easy
for newcomers it is worth having a documented tool.
Cheers,
Mark.
On Fri, 5 Dec 2003 [EMAIL PROTECTED] wrote:
> hi,
>
> rsync won`t help because the userrights (direcotry specially) eventuelly get
> wrong, if i copy from hostmachine to hostmachine.
>
>
> I have no idea how to copy "correctly" between two server.
>
>
> Greetings
> Oliver
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Roderick A.
> Anderson
> Sent: Freitag, 5. Dezember 2003 19:57
> To: [EMAIL PROTECTED]
> Subject: Re: [vserver] Copying vservers
>
>
> I have a request for Mark Lawrence. I've looked at and wanted to use the
> vserver-copy script you wrote but it doesn't quite (or at least doesn't
> appear to) do a copy from one partition to another. I have very little
> experience with rsync so hesitate to fiddle with it.
>
>
> Best,
> Rod
> --
> "Open Source Software - You usually get more than you pay for..."
> "Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL"
>
>
> ___
> Vserver mailing list
> [EMAIL PROTECTED]
> http://list.linux-vserver.org/mailman/listinfo/vserver
>
>
>
> ___
> Vserver mailing list
> [EMAIL PROTECTED]
> http://list.linux-vserver.org/mailman/listinfo/vserver
>
>
#!/bin/sh
#
# Copyright (C) 2002, Mark Lawrence <[EMAIL PROTECTED]>.
# Licence: GPL
#
# Copy/Sync a virtual host from one machine to another
#
# History:
#
# 2003-02-23: Version 0.2 - Mark Lawrence
# - Set ONBOOT to "no" in the original .conf file when the "-s" flag is
# used so that if/when you reboot the source roothost you don't have the
# same vserver and IP address running on two machines.
#
# 2003-03-04: Version 0.3 - Mark lawrence
# - Changed all checks for [ "" != "$var" ] into [ -n|-z "$var" ]. "" doesn't
# seem to work for bash on the Sparc architecture.
# - Changed $ssh variable into $shcmd.
#
# 2003-04-04: Version 0.4 - Mark lawrence
# - Set "ONBOOT=no" in the destination .conf file when --startstop
# is not used, in case the destination roothost reboots. We don't
# want two copies of a vserver running at the same time.
#
# 2003-06-24: Version 0.5 - Mark lawrence
# - Added --numeric-ids to the main rsync call, because
# otherwise the uids could be translated/change during the copy.
# - Aadded --delete to the main rsync call because I found out the
# hard way that things like mail queue files would always grow.
# Ie: mails in the queue are copied, and will be delivered again if
# you backup from the copy, or start the copy of the vserver on another
# machine.
VERSION="0.5"
umask 022
me=${0##*/}
### Helper functions ###
# Save stdin and stdout for later use
exec 3>&1
exec 4>&2
noninteractive () {
exec &> /dev/null
}
interactive () {
exec 1>&3
exec 2>&4
}
info () {
! $quiet && echo "I: $me: $1" >&3
}
warn () {
! $quiet && echo "W: $me: $1" >&4
}
error () {
! $quiet && echo "E: $me: $2" >&4
rm -f $tmpf
exit $1
}
### Usage/Info functions ###
usage () {
cat <&2
Usage: $me [-hVvqidrRs] vserver newname
$me [-hVvqidrRs] vserver host:[newname]
(Use -h for help)
EOF
}
full_usage () {
usage
cat <
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or (at
your option) any later version.
EOF
}
### Default values and Command line options ###
stopstart=(false)
verbose=(false)
quiet=(false)
shcmd="ssh"
rsflag="-e"
rsh=(false)
colon=":"
domain=""
ip=""
vsroot="/vservers"
if [ $# -eq 0 ]; then # Script invoked with no command-line args?
usage
exit 1
fi
temp=$(getopt -o hVvqd:i:rRs --long
help,version,verbose,quiet,domain:,ip:,vsroot,rsh,stopstart, -n $me -- "$@")
if [ $? -ne 0 ]; then
echo " (See -h for help)"
exit 1
fi
# Note the quotes around `$temp': they are essential!
eval set -- "$temp"
while true; do
case "$1" in
-h|--help) full_usage
exit 1
;;
-V|--version) full_version
exit 1
;;
-v|--verbose) verbose=(true)
shift
;;
-q|--quiet) quiet=(true)
shift
