1179533107 Q * Aiken Remote host closed the connection
1179533394 J * Wuher Wuher@c-67-177-29-11.hsd1.ut.comcast.net
1179533675 M * Wuher I have an nfs mounted dir on the parent box that I want to use within a vserver.  I add it to my /etc/vservers/name/fstab and reboot, and it won't mount.  I've done the same thing previously with smb mounted shares and it worked fine - has anyone done something similar, or have any insights?
1179533742 M * daniel_hozac you might want to try it with fstab.remote.
1179533786 M * Wuher /etc/vservers/name/fstab on the parent box?
1179533792 M * Wuher Er.. fstab.remote within the parent?
1179533881 M * Wuher Or do you mean the /etc/fstab within the vserver?
1179533946 M * daniel_hozac the one on the host, of course.
1179533976 Q * ruskie Read error: Connection reset by peer
1179534008 M * Wuher I don't have an fstab.remote file - where do I put that?
1179534151 M * Wuher Hm.. I think I found the problem.  The vserver doesn't treat it as a local mount, it still treats it as an nfs mount.. so it tries to mount the nfs share (which I'd guess is simply a result of how nfs works), but fails because it doesn't have access.
1179534243 M * Wuher I wonder if I mount it again locally if that will fix it.
1179534262 M * daniel_hozac what?
1179534283 M * daniel_hozac what's a "local mount"?
1179534303 M * Wuher Just a mount on the parent box..
1179534338 M * Wuher For instance, when you have a smb share mounted on the host box, add it to the fstab for the vserver, it looks just like any other mount on the host would.
1179534353 M * daniel_hozac hmm?
1179534394 M * daniel_hozac looks like that where?
1179534402 M * Wuher within the guest/vserver.
1179534450 M * daniel_hozac i guess i'm not understanding.
1179534481 M * daniel_hozac what are you talking about?
1179534584 M * Wuher ok.. so I have box A, which is a fileserver exporting an nfs share.  box B is the vserver host, which mounts the nfs share at /fileserver.  I add /fileserver to /etc/vservers/name/fstab on box B, for the vserver to see it.
1179534651 M * Wuher The vserver ('box C') ends up trying to mount it, and has an entry in its /etc/fstab for it; however, it can't mount it.  The entry in its fstab is 10.x.x.x:/path -- not the mount from the host.
1179534674 M * daniel_hozac what are you adding to the fstab?
1179534689 M * Wuher The /fileserver mount point from the parent.
1179534714 M * daniel_hozac well, what i meant was, what does the line look like?
1179534753 M * Wuher My /etc/fstab on the host: 10.2.1.2:/fileserver    /fileserver     nfs     rw      0       0
1179534779 M * daniel_hozac and you use the same in the guest's fstab?
1179534790 M * Wuher Then /etc/vservers/name/fstab on the host:  none    /fileserver     /fileserver     auto    rbind   0       0
1179534809 M * Wuher (Also have tried the second "/fileserver" as simply "fileserver")
1179534828 M * Wuher The /etc/fstab on the vserver: 10.2.1.2:/fileserver    /fileserver     nfs     rw      0       0
1179534829 M * daniel_hozac umm, surely that should be /fileserver /fileserver none?
1179534851 M * Wuher That's not how any of the other entries appear
1179534862 M * Wuher For example, none    /proc           proc    defaults                0 0
1179534884 M * daniel_hozac the fstab is the same as any other.
1179534919 M * daniel_hozac source destination filesystem options backup check
1179534922 M * Wuher Well, from a newvserver build, that's how the fstab on the parent is always written for any of the 20+ vservers I have running..
1179534932 M * daniel_hozac the none is just the source for that mount.
1179534939 M * daniel_hozac in your case, that would be /fileserver...
1179534983 M * Wuher So.. /fileserver /fileserver auto rbind 0 0
1179535043 M * Wuher I was just modeling it after what was there already (which has worked previously for smb mounts, or mounting other partitions from the host)
1179535085 M * Wuher ok, I changed it and restarted the vserver - same problem.
1179535087 M * daniel_hozac putting none at the front would never have worked.
1179535102 M * daniel_hozac what _is_ the problem?
1179535138 M * Wuher the vserver doesn't mount the nfs share, because it treats it like an nfs share.
1179535140 M * daniel_hozac btw, you really should start using vserver .. build instead of newvserver.
1179535150 M * daniel_hozac what makes you say that?
1179535169 M * Wuher the vserver is on a public IP address, which doesn't have access to the nfs share.
1179535200 M * daniel_hozac well, you'll have to change that.
1179535207 M * Wuher the host has a public and internal IP, and mounts it from an internal IP on the file server across the gigabit network intead of the public 100mbit connection which uses bandwidth... ;)
1179535229 M * daniel_hozac the guest is only allowed to use it's own IP addresses, and NFS packets generated by the guest will have one of those...
1179535240 M * Wuher right.. but it shouldn't even have to do nfs.
1179535259 M * daniel_hozac how else would you expect it to work?
1179535263 M * Wuher The problem arises from the vserver treating it like an nfs share, instead of just any other mount point on the parent (including smb mounts)
1179535272 M * daniel_hozac no.
1179535289 M * daniel_hozac the "problem" is that NFS generates the packets from within the context.
1179535295 M * Wuher Right.
1179535303 M * daniel_hozac which limits it to the guest's IP addresses.
1179535320 M * Wuher Just differences between nfs and smb, which is what I was wondering.
1179535339 M * Wuher So I need to add a second interface with an internal IP to the vserver.
1179535341 M * daniel_hozac IIRC CIFS launches a kernel thread for all communication with the server.
1179535539 M * Wuher ok, thanks for the help :)
1179535570 M * daniel_hozac btw, you could always NAT those packets.
1179535592 M * Wuher True
1179535771 M * Wuher Adding a 2nd interface to the guest is probably a much more portable solution though :)
1179537651 J * dna ~naucki@220-239-dsl.kielnet.net
1179537677 Q * bzed Quit: Leaving
1179537729 Q * dna 
1179541978 M * Bertl_oO finally off to bed now ... have a good one everyone!
1179541985 N * Bertl_oO Bertl_zZ
1179542081 N * ensc Guest27
1179542091 J * ensc ~irc-ensc@p54B4EC8A.dip.t-dialin.net
1179542199 Q * Guest27 Ping timeout: 480 seconds
1179543720 Q * Piet__ Quit: Piet__
1179544444 Q * duckx Remote host closed the connection
1179550998 M * Vesa_ Good morning...  I do not intend to start a war, but can you guys explain, how linux-vserver is better than OpenVZ?
1179555454 J * DreamerC ~dreamerc@125-225-98-9.dynamic.hinet.net
1179557914 J * Aiken ~james@ppp222-137.lns2.bne1.internode.on.net
1179558183 J * ktwilight ~ktwilight@135.200-66-87.adsl-static.isp.belgacom.be
1179558183 Q * ktwilight_ Read error: Connection reset by peer
1179558593 Q * DreamerC Quit: leaving
1179559592 Q * ahuman Remote host closed the connection
1179559868 Q * Guy- Ping timeout: 480 seconds
1179560944 J * dna ~naucki@231-212-dsl.kielnet.net
1179561934 J * bonbons ~bonbons@ppp-110-112.adsl.restena.lu
1179562148 Q * zLinux Ping timeout: 480 seconds
1179562735 J * zLinux ~zLinux@88.213.43.14
1179566382 J * Sebrelian ~root@slycl346.lyceu.net
1179566468 M * Sebrelian Hi all
1179566505 Q * Sebrelian Remote host closed the connection
1179566844 Q * transacid Ping timeout: 480 seconds
1179567063 J * Sebrelian ~root@slycl346.lyceu.net
1179567147 M * Sebrelian Hi all I have a question about NFS who can help me?  
1179567209 Q * Sebrelian Remote host closed the connection
1179568050 Q * brcc_ Ping timeout: 480 seconds
1179568579 J * transacid ~transacid@transacid.de
1179568994 Q * dna Quit: Verlassend
1179569135 M * transacid does the vserver have a su - process in the host?
1179569298 M * arachnist vserver foo exec ?
1179569370 M * transacid no i mean, i have a suspicious su - process in the host and i dunno where it comes froms
1179569383 M * transacid it can't be killed, it just forks out of nowhere
1179569404 M * arachnist ah, no idea
1179569413 M * transacid http://phpfi.com/235260
1179569699 M * transacid it scares me couse i can't figure out where it comes from
1179569714 M * arachnist and what does pstree say?
1179569780 M * transacid it's a child of init
1179570512 M * transacid oh i think i know what it is
1179570514 J * akaihola ~akaihola@katti.ambitone.com
1179570691 M * akaihola I'm running Ubuntu Dapper LTS. What's the current wisdom of which kernel version to run with Linux-VServer on that platform? And Ubuntu patched kernel or vanilla from kernel.org? Patch and make kernel or pre-packaged kernels available?
1179570976 M * transacid akaihola: vanilla
1179570990 M * transacid and the vserver-patches can be found here 
1179570994 M * transacid http://linux-vserver.org/
1179571024 M * akaihola transacid: Yes, I found them and noticed that if I want to run VServer 2.2.0, I need to use kernel 2.6.19 or 2.6.20.
1179571062 M * akaihola transacid: I suppose I need to check if 2.6.19 or 2.6.20 vanilla is safe to run with Dapper.
1179571078 M * transacid best choice at the moment ist: vanilla 2.6.20.11 and vserver-patch 2.2.0
1179571106 M * transacid what is dapper?
1179571123 M * akaihola transacid: Ubuntu 6.06 Long Time Support
1179571155 M * transacid is it a kernel patch?
1179571192 M * akaihola transacid: It's a Linux distribution.
1179571221 M * transacid yeah i know waht ubuntu is, i thought dapper would be a special patch
1179571232 M * akaihola transacid: which offers 2.6.15 and 2.6.17 kernel binaries in its repository
1179571236 M * transacid but y wouldn't a vanilla kernel work with ubuntu
1179571247 M * akaihola transacid. Dapper is just the codename for Ubuntu 6.06.
1179571253 M * transacid ok i see
1179571266 M * akaihola transacid: I don't know, so I just want to make sure.
1179571298 M * akaihola transacid: hasn't e.g. the devfs>udev transition caused incompatibilities between kernel versions and distibution versions?
1179571301 M * transacid get the above mentioned sources from kernel.org and you'll be fine
1179571318 M * transacid hmm i recommend to use udev anyway
1179571330 M * transacid devfs is depricated imo
1179571375 M * akaihola transacid: I mentioned devfs/udev just as an example of something which has prevented people from running arbitrary kernel versions with a distro version of choice.
1179571395 M * transacid akaihola: so what do you use at the moment?
1179571404 M * transacid i dunno much about ubuntu
1179571419 M * transacid i'm running gentoo and debian
1179571436 M * akaihola transacid: right now I'm using Ubuntu 6.06's stock 2.6.15 kernel
1179571459 M * transacid yes, but does it use devfs or udev?
1179571477 M * akaihola udev
1179571520 M * akaihola Ubuntu is of course very much like Debian.
1179571540 M * transacid so i dun think there will be any problem then
1179572127 Q * virtuoso Read error: Connection reset by peer
1179572413 J * ekc ~ekc@netblock-66-245-252-180.dslextreme.com
1179572552 M * ekc Does anyone know why 'vserver test1 start' would report 'vserver test1 already running' and 'vserver test1 stop' would report 'namespace: vc_enter_namespace(): no such process'?
1179572578 M * ekc vserver 'test1' has been running fine for the last several days. but, after I stopped it, i'm getting this odd behaviour.
1179572608 M * ekc fyi, vserver 'test1' has no ctxid entry under /proc/virtual
1179572627 M * ekc i'm running 2.6.20.3-vs2.2.0-rc19
1179572680 M * ekc util-vserver is 0.30.212
1179572887 J * ema ~ema@rtfm.galliera.it
1179573375 Q * ekc Ping timeout: 480 seconds
1179573428 J * ekc ~ekc@netblock-66-245-252-180.dslextreme.com
1179573521 J * PowerKe_ ~tom@d54C13E4B.access.telenet.be
1179573799 Q * PowerKe Ping timeout: 480 seconds
1179573951 N * PowerKe_ PowerKe
1179574028 Q * ekc Remote host closed the connection
1179574053 Q * Aiken Remote host closed the connection
1179574290 J * phedny_ ~mark@ip56538143.direct-adsl.nl
1179574380 J * ekc ~ekc@216.129.126.130
1179574688 Q * phedny Ping timeout: 480 seconds
1179574767 J * brcc_ bruce@i.am.someasshole.com
1179575859 Q * ekc Quit: Lost terminal
1179576308 N * phedny_ phedny
1179576758 J * ekc ~ekc@216.129.126.130
1179576782 M * ekc OK. I solved my problem.
1179576827 M * ekc What was happening was this: vserver 'test1' had /etc/vservers/test1/run and /vdirbase pointing to a different vserver that was already running.
1179576835 M * ekc silly mistake on my part
1179576837 M * ekc oh well
1179576879 Q * ekc 
1179576935 Q * ktwilight Quit: dead
1179580702 Q * ema Quit: leaving
1179581866 N * Bertl_zZ Bertl
1179581874 M * Bertl morning folks!
1179581893 M * daniel_hozac morning Bertl
1179581911 M * Bertl how's going?
1179581964 M * daniel_hozac fine thanks. you?
1179581990 M * Bertl swamped with work .. but that is not unusual after a 4 week vacation :)
1179581999 M * daniel_hozac hehe, indeed.
1179582001 M * Bertl besides that, quite fine ...
1179582042 M * Bertl did we get any feedback for 2.6.21, except for the tty issue?
1179582063 M * daniel_hozac not that i've seen.
1179582148 M * Bertl the sysfs stuff is worked on in mainline, and should get a fix for .22, right?
1179582185 M * daniel_hozac hmm? what sysfs stuff?
1179582202 M * Bertl the dentries going mad/disappearing ...
1179582262 M * Bertl which caused the kernel oops with BUG_ON(dent_a != dent_a->b->a
1179582264 M * daniel_hozac well, i certainly hope that's something which would be getting fixed...
1179582603 M * Bertl as far as I got it, the final fix will be in .23 or so
1179582671 M * daniel_hozac so .21 is not something you'd recommend for production use?
1179582691 J * duckx ~Duck@tox.dyndns.org
1179582752 M * Bertl probably not, I've still kept my production systems on 2.6.19.x for now, had a (not really substantiated) bad feeling about 2.6.20, and 2.6.21 is almost untested ...
1179583549 M * daniel_hozac hehe.
1179584324 M * Bertl but maybe I'm just getting old :)
1179584424 M * Wonka lol
1179584675 M * Bertl wow, I'm deeply impressed, I have a (somewhat older) motherboard from tyan here, which has a perfect (bug-free) DSDT ... anybody else with non intel mobos/bios and correct DSDT?
1179584714 M * Bertl about:blank
1179584745 M * Bertl (and I have the wrong keyboard here too :)
1179585230 J * Aleks ~Antony@213.208.38.17
1179585246 M * Aleks Hi All
1179585257 M * Bertl welcome Aleks!
1179585258 M * Aleks I have a question about VServer over NFS
1179585270 M * Bertl let's hear then ...
1179585319 M * Aleks I want to put /vserver dir on NFS storage and mount them on VServer host sysatem
1179585344 M * Bertl okay, nothing unusual so far ... Lycos does that too :)
1179585385 M * Aleks every thing as I see ok, but I have problem with disklimit over nfs
1179585410 M * Bertl ah, you are using tagxid for the nfs?
1179585418 M * Aleks exactli...
1179585425 M * Bertl if so, you have to make sure that the NFS server is also patched
1179585468 M * Aleks it is patched. I do not have problem under 2.6.17 kernel.... but with 2.6.18-19 I have
1179585494 M * Bertl that's interesting ... care to share the tested versions and issues you see?
1179585505 M * Bertl (patch versions that is)
1179585521 M * Aleks as I see VServer2.0.1 is ok but not 2.1.0 and 2.2.0
1179585567 M * Bertl okay, so you tested with 2.6.19.x-vs2.2.0 (final)?
1179585570 M * Aleks Is ther a way to patch 2.6.18 or 19 kernel with VServer2.0.1
1179585579 M * Aleks yeap
1179585591 M * Bertl okay, what _are_ the issues? can you describe them?
1179585655 M * Aleks issue is "not-working" tagxid as i see )
1179585672 M * Aleks which parameters should I enable on NFS storagE?
1179585684 M * Bertl okay, how did you test that? i.e. do you have a simple test case?
1179585698 M * Bertl basically you want tagxid enabled on all ends
1179585726 M * Bertl i.e. the filers _real_ filesystem and the nfs filesystem
1179585797 M * Aleks yea... I enabled tagxid mount on local system of NFS, after that mount with tagxid from Host system
1179585833 M * Bertl okay, let's call the machine which does provide the NFS filer (to simplify terminology)
1179585848 M * Bertl s/NFS/NFS,/
1179585857 M * Aleks it is working with 2.6.17. and not with 2.6.18 or 20
1179585863 M * Aleks :) ok
1179585885 M * Bertl you have a few moments to test a few things with 2.2.0?
1179585900 M * Aleks I enabled local-mount tagxid on filer
1179585924 M * Bertl i.e. are you interested in getting 2.2.0 fixed (if broken)?
1179585941 M * Aleks yea.
1179585961 M * Bertl okay, then let's do a few test on your system, shall we? 
1179585970 M * Aleks or for example in 2.1.0
1179585976 M * Aleks lets do
1179585993 M * Bertl okay, so let's get 2.2.0 booted on both machines, the filer and the host
1179586002 M * Aleks it is
1179586017 M * Bertl okay, great, 2.6.19.x?
1179586027 M * Aleks yea :)
1179586045 M * Bertl good, you have a recent testme.sh?
1179586048 M * Aleks FYI 2.6.19.7
1179586064 M * Aleks no.. let me download it
1179586272 M * Bertl http://vserver.13thfloor.at/Stuff/SCRIPT/testme.sh
1179586285 M * Aleks on filer i got chcontext is working.
1179586295 M * Aleks and chbind failed!
1179586334 M * Aleks on hostsystem every thing is green :)
1179586373 M * matti Hi Bertl
1179586408 M * Bertl Aleks: interesting .. try to run it with -d (on both systems) and upload that to paste.linux-vserver.org please
1179586417 M * Bertl matti: hey! how's going?
1179586431 M * matti Bertl: I've Intel BadAxe 2 on my desktop, and DSDT is broken.
1179586440 M * matti At work.
1179586476 M * Bertl hehe, well, I thought at least intel would have proper dsdt info
1179586484 M * matti Me too :)
1179586507 M * matti I'd corrected it, but it was a bit dissapointing.
1179586508 M * matti :)
1179586523 M * matti Bertl: Not too good - life is a crap :)
1179586532 M * Bertl matti: how so?
1179586908 M * Aleks Bertl: hm.. and on host and on filer everi thing green. I have reinstalled util-vserver
1179586953 M * Aleks should I send output?
1179587148 M * Bertl yep, please _upload_ them to the pastebin
1179587160 M * Bertl (i.e. do not paste them here :)
1179587239 M * Aleks :))))))))))))))))))))))))))) 
1179587248 M * Aleks you have them:)
1179587303 M * Bertl excellent! tx!
1179587331 M * Aleks Thank you, that you trying to help me ;)
1179587445 M * Bertl np, okay, can you check something in the kernel config for me, for both machines?
1179587473 M * Aleks yea
1179587512 M * Bertl I'm interested in 'grep NFSD .config' (please upload again)
1179587550 M * Aleks ok.. do you have enough space on your paste server? :)))))))))))))
1179587558 P * click [IRSSI]
1179587563 M * Aleks kidding I'll do that
1179587568 M * Bertl :)
1179587587 J * Guy- ZpCdyiWbqo@chardonnay.math.bme.hu
1179587590 M * Bertl Aleks: if not, we'll make some room for you :)
1179587597 M * Bertl wb Guy-!
1179587611 M * Guy- hi
1179587697 J * click click@ti511110a080-0476.bb.online.no
1179587704 M * Guy- I think I found a data corruption bug related to hashified files
1179587718 M * Bertl wb click! LTNS!
1179587723 M * Bertl Guy-: let's hear ...
1179587730 M * Guy- when I open a hashified file in a guest using joe, it suddenly only contains zeroes
1179587733 M * Aleks Bertl: you have it
1179587779 M * click bertl: just a bit, been busy with tons of stuff here
1179587833 M * Guy- Bertl: this is 2.6.20.6-vs2.2.0, running 32bit guests on a 64bit host
1179587867 M * Guy- Bertl: the filesystem is xfs, which is on lvm, which is on LUKS (dm-crypt)
1179587876 M * Guy- (not sure if this matters)
1179587899 M * Bertl Guy-: well, for sure it won't hurt to know :)
1179587919 M * Bertl click: me2, me2 ...
1179587940 M * Bertl Aleks: okay, checking something in the code now, will take a few minutes
1179587960 M * click brb, got to grab some food
1179587973 M * Guy- Bertl: it's reproducible too
1179588003 M * Bertl Aleks: ah, you could do a test for me in the meantime: create a file (touch?) on the filer, then chxid it to something (like 666), and lsxid it on the host (nfs client)
1179588048 M * Aleks ok fine :)
1179588201 M * Aleks I get "!!ERR!!               TestFile" on Host
1179588258 M * Bertl okay, that is kind of what I thought ... let's check the following too:
1179588303 M * Bertl check /proc/mounts on the host and filer, and identify the lines related to the filesystem, then upload them
1179588315 M * Guy- Bertl: but only with joe. vim is fine...
1179588374 M * Bertl Guy-: hmm, maybe joe does something strange with the file first, and keeps the handle around, changing it to write lateron?
1179588401 M * Bertl Guy-: would be interesting to get an 'strace -fF -o joe.trace joe ...' when it does that ...
1179588440 M * Guy- I just did that
1179588454 M * Guy- open("e2initrd_helper", O_RDWR|O_LARGEFILE) = 3
1179588454 M * Guy- close(3)                                = 0
1179588454 M * Guy- open("e2initrd_helper", O_RDONLY|O_LARGEFILE) = 3
1179588470 M * Guy- (I was editing e2initrd_helper)
1179588480 M * Bertl okay, can you upload the complete strace somewhere?
1179588483 M * Guy- sure
1179588501 M * Bertl daniel_hozac: did we decide to remove the nfs tagging from 2.2.0?
1179588709 M * Aleks You have now too :)
1179588716 M * Aleks *it
1179588720 M * Bertl tx
1179588751 J * ktwilight ~ktwilight@135.200-66-87.adsl-static.isp.belgacom.be
1179588767 M * Aleks np
1179588781 M * Bertl Aleks: did you, by any chance, build your kernel with debugging enabled? e.g. for rpc and nfs(d)?
1179588786 M * Bertl wb ktwilight!
1179588803 M * ktwilight thanks :)
1179588825 M * Aleks nope :(
1179588837 M * Aleks do we need it?
1179588936 M * Guy- Bertl: http://chardonnay.math.bme.hu/~korn/tmp/joe.vserver.corruption.strace.log
1179589057 M * matti Heheh.
1179589151 J * marinusisrael ~marinusis@ip503cfa01.speed.planet.nl
1179589193 M * Bertl welcome marinusisrael!
1179589198 M * marinusisrael hi
1179589220 M * marinusisrael i have a question i hope you can answer :)
1179589320 M * Bertl Guy-: interesting, does that happen only with 32bit guests? (or didn't you try with a 64bit one yet?)
1179589336 M * marinusisrael i made a new guest on a host system thats been running for quite a while with some other guests. but on the new guest i can't chown /proc. On the older guests thats no problem... I did run vprocunhide..
1179589344 M * Guy- Bertl: I have no 64bit guests on this box at the moment
1179589376 M * Guy- Bertl: I can install one to see how it fares, but that'll have to wait a few days
1179589385 M * Bertl marinusisrael: chown the /proc dir or something inside the procfs itself? (the latter one is forbidden for good reason)
1179589396 M * marinusisrael chown the /proc dir
1179589423 M * Bertl Guy-: you should be able to get a debian 64bit within a few minutes, I'd say (with util-vserver)
1179589435 M * marinusisrael bertl: filesystem package of FC6 tries to do that but fails
1179589465 M * Guy- Bertl: yes, but I'm in the middle of a service migration here :)
1179589474 M * Bertl marinusisrael: I guess it fails because it doesn't reach the dir as long as /proc is mounted there ...
1179589497 M * Bertl Guy-: okay, np, please try and let me know when you're done ... no need to hurry ...
1179589505 M * Guy- Bertl: I will
1179589515 M * marinusisrael Bertl: but isnt it weird that it works in the one guest but not in the newly created?
1179589554 M * Bertl yes, that is kind of weird, and might have several reasons, do you want to investigate?
1179589575 M * marinusisrael yes please
1179589595 M * Bertl okay, first, do you get any messages in 'dmesg'?
1179589609 M * Bertl (which might be related, e.g. vxW messages)
1179589639 M * matti :)
1179589641 M * matti Yay.
1179589656 A * matti created live flash video streaming for fun :P
1179589661 M * matti From my work :)
1179589670 M * Bertl congrats!
1179589675 M * matti Thanks :)
1179589683 A * matti is a bit bored ;D
1179589714 M * marinusisrael bertl: no, there doesnt seem to be anything out of order in there
1179589757 M * Aleks Bertl: do you need anything else?
1179589781 M * daniel_hozac Bertl: re NFS tagging, i think so.
1179589785 Q * akaihola Read error: Connection reset by peer
1179589809 Q * Aleks 
1179589824 M * daniel_hozac Bertl: or maybe we just discussed it, because i can't find it in the changelog.
1179589834 J * Aleks ~Antony@213.208.38.17
1179589892 M * Aleks Bertl: I had problems with connection :( did i miss something? :)
1179589904 M * daniel_hozac no.
1179590053 M * Aleks daniel_hozac: tx:) As I understand there is no way to have tagxid via NFS with 2.2.0?
1179590261 J * mattzerah_ ~matt@121.50.222.55
1179590261 Q * mattzerah Read error: Connection reset by peer
1179590347 M * daniel_hozac Aleks: i wouldn't be so sure.
1179590356 M * Bertl daniel_hozac: the funny thing is, we still seem to carry the config for that, but no code which uses it
1179590379 M * Aleks :))))))
1179590383 M * Bertl Aleks: 2.3.x should still have it (or at least I think we will put it there :)
1179590390 M * daniel_hozac CONFIG_DX_TAG_NFSD in include/linux/vserver/tag.h?
1179590411 M * daniel_hozac (whereas the config option is CONFIG_TAG_NFSD)
1179590434 M * Aleks OK, in that case how can I get my system working with 2.6.19 Kernel?:)
1179590446 M * Bertl daniel_hozac: ah, that might explain a few things ...
1179590542 M * daniel_hozac yeah. fixing that should make it work again, no?
1179590571 M * Aleks Is there a possibility to patch 2.6.19 with VS2.0.1 (some part)?
1179590577 M * Bertl daniel_hozac: yep, we have the other code in place ...
1179590598 M * Bertl Aleks: give us a few minutes, and you get a patch for vs2.2.0 :)
1179590607 M * Aleks ok thanks :)
1179591335 M * marinusisrael Bertl: I found an interesting point. I just created a new guest and chown on /proc worked fine. Then i updated the guest from FC3 to FC6 and after the upgrade it does not work anymore
1179592175 M * Bertl aha .. strange ...
1179592226 J * dna ~naucki@157-249-dsl.kielnet.net
1179592549 Q * tanjix Ping timeout: 480 seconds
1179592578 M * marinusisrael mm, putting back an older version of chown solved the problem with a direct chown command
1179592590 M * marinusisrael but cpio still gives an error
1179592593 M * marinusisrael any ideas?
1179592652 M * Bertl that sounds really interesting ... let's try the following please:
1179592678 M * Bertl with the old and new chown, do: 'strace -fF -o chown.trace chown ....'
1179592703 M * Bertl then please upload the trace of the working and failing chown to paste.linux-vserver.org
1179592713 M * marinusisrael ok let me try that
1179592872 M * Aleks Bertl: Is it Possible to have 2.0.1 on 2.6.19 kernel? 
1179592911 M * Aleks because as I see old util Vserver cannot wark with 2.2.0 too
1179592938 M * Aleks *work
1179592980 M * Bertl no, 2.0.x is pre 2.6.19 (end of life)
1179592995 M * Bertl but older tools should work with 2.2.0 fine
1179593017 M * Bertl besides that, you might consider upgrading the tools anyway to make use of the new features
1179593026 M * Aleks :))))))
1179593080 M * Aleks I want at firt keep my system working :)  and what about 2.0.1 on 2.6.18?
1179593150 M * daniel_hozac there's 2.0.3-rc1 for 2.6.18.
1179593210 M * Bertl Aleks: as I said, you'll get a trivial patch in a few minutes, just trying to test it first :)
1179593230 M * Aleks ok :) I'll do that in any case ))))
1179593382 M * Aleks daniel_hozac: it is rc, do you have relased one or not?
1179593509 M * marinusisrael Bertl: I put the traces there
1179593521 M * daniel_hozac marinusisrael: which is which?
1179593539 M * marinusisrael daniel_hozac: FC6 is the non working one, FC3 works
1179593591 M * daniel_hozac looks like the FC3 one has some intelligence to not set it if it's already set.
1179593635 J * virtuoso ~s0t0na@80.253.205.251
1179593644 M * daniel_hozac does the cpio error matter?
1179593668 M * daniel_hozac i.e. does it fail the transaction?
1179593675 M * marinusisrael yes
1179593684 M * marinusisrael the rpm doesnt get installed
1179593751 M * daniel_hozac you could probably work around it by setting %_netsharedpath
1179593843 M * marinusisrael how do i do that?
1179593892 M * daniel_hozac echo "%_netsharedpath /proc" >> /etc/rpm/macros.proc
1179593929 M * marinusisrael still same error
1179593935 M * marinusisrael you want a trace of the rpm command?
1179593971 M * daniel_hozac that's odd.
1179593995 M * daniel_hozac it shouldn't touch files in %_netsharedpath.
1179594029 J * rheylew_ ~rheylew@static-66-16-237-46.dsl.cavtel.net
1179594121 M * marinusisrael error: unpacking of archive failed on file /proc: cpio: chown failed - Operation not permitted :S
1179594138 Q * rheylew_ Remote host closed the connection
1179594287 M * marinusisrael just put the rpm trace in the pastebin
1179594315 M * marinusisrael hmm, its too big
1179594346 M * daniel_hozac rpm --showrc | grep netsharedpath shows it, right?
1179594382 M * marinusisrael no /proc
1179594404 M * daniel_hozac what does it have then?
1179594429 M * marinusisrael [root@tina ~]# rpm --showrc | grep netsharedpath
1179594429 M * marinusisrael -14: _netsharedpath     /dev:/etc/rc.d/init.d/halt:/sbin/new-kernel-pkg:/usr/bin/rhgb-client
1179594432 M * daniel_hozac ah.
1179594454 M * daniel_hozac grep _netsharedpath /etc/rpm/macros.*, edit the one which already exists.
1179594497 M * Bertl Aleks: okay, I cannot test it here (too much troubles with my build system, but here is the trivial patch: http://vserver.13thfloor.at/Experimental/delta-nfsd-fix01.diff
1179594539 M * marinusisrael hey hey! It works :-)
1179594552 J * ema ~ema@rtfm.galliera.it
1179594572 M * Aleks guys sorry some times ago I saw on your site a table which is describing which feature is supported with which version of VServer 
1179594592 M * Aleks now I'm trying to find it but i cannot:(
1179594605 M * daniel_hozac http://linux-vserver.org/Feature_Matrix
1179594608 M * Aleks Bertl: I'll do test now
1179594629 M * Aleks thanks for link :)
1179594943 M * Aleks Bertl: I should patch only Filer kernel. An I true?
1179594951 M * daniel_hozac Aleks: both of them.
1179594997 M * Aleks ok. it will take time. I'll let you know about results
1179595030 M * Bertl Aleks: np, thank you for reporting and testing!
1179595097 M * Aleks np. thank you for patch.
1179595229 M * Aleks question: is there release after patch-2.6.18.5-vs2.0.3-rc1.diff? ot is latest thing on 2.0.X? is it sable? or which one of rc of 2.0.X is stablest?
1179595560 M * marinusisrael Bertl, daniel; everything seems to be working now, thanks for the help!
1179595695 M * Bertl marinusisrael: you're welcome!
1179595751 M * Bertl Aleks: daniel_hozac> there's 2.0.3-rc1 for 2.6.18.
1179595775 M * Bertl Aleks: so that seems to be the last one :)
1179595829 M * Aleks :))))) thanks. in any case what you suggest which one I shoud use. let's say the best of them :)
1179595939 M * Bertl if vs2.2.0 + patch works for you, you should go with that one
1179595956 M * Bertl it was extensively tested and includes all the proven stable features
1179596116 M * Aleks for sure :)  
1179596135 M * daniel_hozac (and it's available for a kernel which is still supported upstream)
1179596176 M * daniel_hozac marinusisrael: that's great!
1179596213 Q * dna Quit: Verlassend
1179596362 M * Aleks the problem is guys that I have system that is working with 2.0, when I tried to upgrade to 2.2 I got several problems.. that is why I'm trying to have at first with new kernel after that with ne VServer :)
1179596418 M * Aleks /is guys/guys is/
1179596425 M * Bertl well, if it _worked_ with 2.0, why upgrade at all? probably had a reason like missing support for old kernels?
1179596509 M * Aleks nope. just trying to have up to date system, but step by step :) 
1179596558 M * Aleks that is why i'm asking about best 2.0.x for k-2.6.18 :)
1179596593 M * daniel_hozac going with 2.6.18 at this point would be a bad idea.
1179596597 M * Bertl hehe, but 2.2.0 and 2.6.19.7 should be up-to-date and really your best choice IMHO
1179596612 M * daniel_hozac 2.6.18 doesn't get security updates or anything anymore.
1179596632 M * daniel_hozac and it's not even the most recent 2.0 patch.
1179596744 M * Aleks ok guys at first I'll try to have system with your new patch :)
1179596924 J * ahuman ~oem@ool-43557e7c.dyn.optonline.net
1179596988 M * Aleks now systems are booting :)
1179597156 M * Aleks nope :(
1179597171 M * Aleks same eeror
1179597228 M * Bertl both machines were updated, and the lsxid (on the host) still says !!ERR!! ?
1179597237 M * Aleks yea
1179597278 M * Bertl okay, give me a few minutes to check the code once again
1179597292 M * Aleks ok thanks
1179597446 M * matti :)
1179597675 M * Bertl daniel_hozac: when exactly does lsxid report !!ERR!!? 
1179597698 M * Bertl Aleks: could you run the lsxid with strace -fF, and upload that for me?
1179597781 M * Bertl Aleks: you said debug is enabled in your kernels, yes? did you also enable VSERVER_DEBUG?
1179597851 M * Aleks no no no.. I said that it is not enabled
1179597901 M * Bertl okay, while we check further stuff, it would be great to enable that and update the kernels, we'll probably need some simple tests/logs
1179597919 M * Aleks ok... you have strace
1179597971 M * Bertl tx
1179597993 M * Aleks only VSERVER_DEBUG?
1179598055 M * Bertl CONFIG_DEBUG_BUGVERBOSE=y
1179598059 M * Bertl CONFIG_DEBUG_INFO=y
1179598062 M * Bertl CONFIG_VSERVER_DEBUG=y
1179598068 M * Bertl that should suffice
1179598254 J * gerrit ~gerrit@c-67-160-146-170.hsd1.or.comcast.net
1179598284 M * Aleks and filer and host?
1179598332 M * Bertl yep
1179598414 M * Aleks ok.. I'll let you know
1179598941 M * Aleks  CONFIG_DEBUG_BUGVERBOSE cannot finde :(
1179599081 M * Aleks in which section is it?
1179599085 M * Bertl depends on CONFIG_DEBUG IIRC
1179599111 M * Bertl but that one is not essential, so don't bother too much
1179599161 M * Aleks I've sent you .config poart.
1179599165 M * Aleks *part
1179599399 M * Bertl if you have CONFIG_VSERVER_DEBUG enabled, it should be fine
1179599415 M * Aleks ok lets compile
1179601116 M * daniel_hozac Bertl: when it errors.
1179601132 M * daniel_hozac Bertl: e.g. if the filesystem isn't mounted with tagxid.
1179601179 M * Bertl daniel_hozac: in the strace above, the command seems to return 0, so I'm a little confused ...
1179601199 M * Aleks I haVE changed something in mount command no (to support tagxid via nfs)
1179601217 M * Bertl Aleks: hmm?
1179601263 M * Aleks with normal mount command you cannot mount via NFS with tagxid
1179601277 M * daniel_hozac Bertl: well, vc_get_iattr still succeeds even with a non-tagxid filesystem, doesn't it?
1179601279 M * Aleks its says "unknown option"
1179601303 M * daniel_hozac it returns !!ERR!! because the returned mask doesn't have IATTR_XID set.
1179601321 M * Bertl daniel_hozac: yep, that is why I didn't understand your 'when it errors.' comment :)
1179601338 M * daniel_hozac well, that's an error IMHO ;)
1179601371 Q * marinusisrael Quit: marinusisrael
1179601410 M * Bertl daniel_hozac: so to clarify, it uses get_iattr, which succeeds, and then checks the mask, if the xid info is missing, it gives the !!ERR!!, right?
1179601424 M * daniel_hozac right.
1179601442 M * Bertl good, that means that the nfs mount had MS_TAGGED off, right?
1179601456 M * daniel_hozac i'd say so.
1179601470 M * daniel_hozac isn't that quite simple to verify by cat /proc/mounts though?
1179601497 M * Bertl Aleks: now the interesting part is, your paste did show 'tag' as the mount options in /proc/mounts, can you confirm that?
1179601529 M * Bertl daniel_hozac: when /proc/mounts shows 'tag' then MS_TAGGED should be on, no?
1179601537 M * daniel_hozac yep...
1179601538 M * Aleks yea
1179601568 M * Bertl so we have some kind of inconsistancy here, either it is on or off but it ccannot be both :)
1179601589 M * daniel_hozac hehe.
1179601594 M * Aleks :))))))
1179601598 M * Bertl we could run into different settings with a --bind mount or so :)
1179601615 M * Aleks i do not have bind
1179601663 M * Bertl Aleks: okay, we have the debug stuff in place?
1179601716 M * Aleks nope... I'm trying to get it....
1179601730 M * Bertl okay, no need to hurry ...
1179601825 M * Aleks vdlimit: vc_get_dlimit(): No such process??? what does it mean? (it from 2.0.1)
1179601850 M * daniel_hozac that there's no disk limit on that filesystem for that guest.
1179601865 M * Bertl i.e. it was not created
1179601877 M * Aleks ah.. ok
1179602963 M * Bertl okay, off for now .. back a little later ...
1179602968 N * Bertl Bertl_oO
1179603089 Q * ema Quit: leaving
1179603163 M * Aleks Guys thank you very much 2.6.18 is working well:)))))
1179603189 M * Aleks daniel: can we contineu testings or we shoud wait Bertl?
1179603308 M * daniel_hozac well, i'm not really up to speed on how NFS, and much less the NFS tagging, works. if Bertl's previous patch didn't work, i guess it's something much less obvious...
1179603447 M * Aleks ok, inthat case what we should do?
1179603473 M * daniel_hozac the fact that lsxid shows !!ERR!! when /proc/mounts says tag is also really weird.
1179603529 M * daniel_hozac what xid tagging are you using?
1179603543 M * Aleks may be I did some thing wrond in "mount" I have changed few lines in its code, as it didnot get "tagxid"
1179603563 M * Aleks sorry? what does it mean? "What xid"?
1179603597 M * daniel_hozac nevermind, i found your testme results.
1179603621 M * daniel_hozac but /proc/mounts shows tag, yes?
1179603634 M * Aleks yea
1179603659 M * daniel_hozac then the kernel understood it.
1179603662 M * Aleks with 2.6.18+2.0.3 it shows tagxid
1179603668 M * Aleks fine
1179603674 M * daniel_hozac tagxid is the old name.
1179603692 M * Aleks ah ok... thanks.
1179603735 M * daniel_hozac could you try using vcmd?
1179603753 M * daniel_hozac should be more verbose than lsxid.
1179603764 M * daniel_hozac might give us a better idea of what's actually happening.
1179603770 M * Aleks vcmd?
1179603772 M * daniel_hozac http://vserver.13thfloor.at/Experimental/TOOLS/vcmd-0.08.tar.bz2
1179604020 M * Aleks I should go may be tomorrow or next time we can investigate the issue.
1179604045 M * daniel_hozac yeah, sure.
1179604090 M * Aleks Bertl & Daniel: thank you very much guys for support :) cu
1179604110 M * daniel_hozac okay, have a good one! cya
1179604121 Q * Aleks 
1179604451 J * derjohn2 ~aj@146.Red-83-53-155.dynamicIP.rima-tde.net
1179604564 J * shedi ~siggi@ftth-237-144.hive.is
1179604659 Q * gerrit Ping timeout: 480 seconds
1179605698 J * gerrit ~gerrit@c-67-160-146-170.hsd1.or.comcast.net
1179605914 Q * derjohn2 Ping timeout: 480 seconds
1179606234 Q * Guy- Ping timeout: 480 seconds
1179606890 J * Aiken ~james@ppp244-220.lns2.bne4.internode.on.net
1179607941 J * tuxmania ~bonbons@ppp-111-14.adsl.restena.lu
1179608258 Q * bonbons Ping timeout: 480 seconds
1179608271 N * tuxmania bonbons
1179608889 J * Piet hiddenserv@tor.noreply.org
1179610157 J * rio ~bl@e177137172.adsl.alicedsl.de
1179610222 M * rio hello, whats recommed to build a new guest? newvserver or vserver build?
1179610237 M * rio and why
1179610459 M * sid3windr the latter, because the former does not exist ;)
1179610464 M * sid3windr (except in debian)
1179610506 M * rio ok right, so why is newvserver not good?
1179610587 M * sid3windr I don't know, it's not supported
1179610598 M * sid3windr does it do anything more than what vserver build does?
1179610606 M * sid3windr it probably does
1179610618 M * rio no i think vserver build has more options
1179610623 M * sid3windr yea
1179610629 M * sid3windr in the beginning I used newvserver and it ran some debconf thingies so you were asked some questions
1179610639 M * sid3windr but vserver .. build is indeed the "real" way to build it
1179610647 M * rio only problem is that there is a bug when i create a guest with vserver build under debian
1179610647 M * sid3windr and probably has more options, and does more than only debian, heh
1179610660 M * sid3windr which is that? (I do it quite frequently)
1179610662 M * rio i found out its already known: https://savannah.nongnu.org/bugs/?18428
1179610691 M * sid3windr hmmmmmm
1179610696 M * sid3windr don't think i've run into that yet :o
1179610709 M * rio you are using debian too=
1179610711 M * sid3windr that's open quite long already :/
1179610712 M * sid3windr yes
1179610718 M * rio yep :(
1179610732 M * rio so it happens when the guest it shut down
1179610981 M * rio btw sid3windr do you know which version of vserver patch is in the current debian release?
1179610985 M * rio 2.2?
1179610995 M * rio cant find any info on it
1179611564 M * sid3windr no idea, I compile my own kernels
1179611928 M * rio ok i see, if i use the latest patch for kernek 2.6.19.7 vanilla do i need some security patches?
1179611944 M * rio or where can i find info about that?
1179611959 M * sid3windr I have no clue :/
1179611961 M * sid3windr but I don't think so.
1179611998 J * ahumane ~oem@ool-43557e7c.dyn.optonline.net
1179612027 M * rio cause i think there was some bugs in netfilter for example
1179612039 M * rio which affect also that version
1179612445 Q * ahuman Ping timeout: 480 seconds
1179613123 J * ahuman ~oem@ool-43557e7c.dyn.optonline.net
1179613128 Q * ahuman Read error: Connection reset by peer
1179614164 J * hardwire` ~bip@rdbck-3234.wasilla.mtaonline.net
1179614514 Q * rio Quit: leaving
1179614549 Q * hardwire Ping timeout: 480 seconds
1179615499 N * hardwire` hardwire
1179616305 Q * bonbons Quit: Leaving
1179616467 Q * Aiken Quit: Leaving
1179617277 J * Piet_ hiddenserv@tor.noreply.org
1179617439 Q * Piet Ping timeout: 480 seconds
1179618555 J * bzed ~bzed@dslb-084-059-103-146.pools.arcor-ip.net