1247529929 J * bzed_ ~bzed@devel.recluse.de
1247530049 Q * bzed_ Remote host closed the connection
1247530084 Q * bzed Read error: Connection reset by peer
1247530107 J * bzed ~bzed@devel.recluse.de
1247530291 J * bzed_ ~bzed@devel.recluse.de
1247530368 Q * bzed Read error: Connection reset by peer
1247530383 N * bzed_ bzed
1247530691 Q * nou Ping timeout: 480 seconds
1247530691 Q * FireEgl Remote host closed the connection
1247531006 Q * hparker Quit: Read error: 104 (Peer reset by connection)
1247531477 J * harry ~harry@d51A461B4.access.telenet.be
1247531541 J * scientes_ ~scientes@174-21-105-2.tukw.qwest.net
1247531571 J * FireEgl Proteus@WTF.4.1.0.c.0.7.4.0.1.0.0.2.ip6.arpa
1247531983 Q * scientes Ping timeout: 480 seconds
1247532272 J * nou Chaton@2001:6f8:328:bbc:6666:6667::
1247534676 Q * mxs Ping timeout: 480 seconds
1247535332 J * Abraxas ~Abraxas@94-224-69-84.access.telenet.be
1247535927 J * mxs mxs@p4FCC9F6C.dip.t-dialin.net
1247536852 J * derjohn_foo ~aj@e180194010.adsl.alicedsl.de
1247537281 Q * derjohn_mob Ping timeout: 480 seconds
1247538243 M * Bertl off to bed now ... have a good one everyone!
1247538248 N * Bertl Bertl_zZ
1247540423 J * saulus_ ~saulus@c135108.adsl.hansenet.de
1247540832 Q * SauLus Ping timeout: 480 seconds
1247540843 N * saulus_ SauLus
1247543876 Q * uva_ Quit: Leaving
1247546820 Q * balbir_ Read error: Connection reset by peer
1247547774 J * balbir_ ~balbir@122.172.7.130
1247553007 Q * allquixotic Remote host closed the connection
1247553173 Q * FireEgl Remote host closed the connection
1247554112 J * FireEgl Proteus@WTF.4.1.0.c.0.7.4.0.1.0.0.2.ip6.arpa
1247554903 Q * FireEgl Ping timeout: 480 seconds
1247555822 J * FireEgl Proteus@Sebastian.Atlantica.CJB.Net
1247556516 Q * imcsk8 Quit: This computer has gone to sleep
1247557381 J * pmenier ~pmenier@ACaen-152-1-22-92.w83-115.abo.wanadoo.fr
1247558715 J * Swordsman ~kohii@pool-71-112-25-59.sttlwa.dsl-w.verizon.net
1247559076 Q * balbir_ Ping timeout: 480 seconds
1247559721 J * imcsk8 ~ichavero@189.155.83.205
1247560520 J * balbir_ ~balbir@122.172.7.130
1247560611 M * Swordsman the wiki's archlinux install page seems to be somewhat outdated
1247560638 M * Swordsman http://linux-vserver.org/Installation_on_ArchLinux#Creating_an_Arch_Linux_VServer
1247560649 M * Swordsman the link to archbootstrap is dead
1247561397 Q * ktwilight_ Read error: Connection reset by peer
1247561404 J * ktwilight ~keliew@61.186-241-81.adsl-dyn.isp.belgacom.be
1247561980 M * kiorky_ Swordsman: it's archlinux which is pretty dead :D
1247561993 N * kiorky_ kiorky
1247562011 M * Swordsman ...?
1247562045 M * Swordsman I'm a bit new to linux, so...
1247562097 M * Swordsman well, I was looking for something to do some virtualization with, and I was looking for a small distro to use
1247562112 M * Swordsman something small, lightweight, and fast, archlinux seemed about right
1247562187 J * Medivh ck@dolphin.serverbox.de
1247562300 M * Swordsman is there a better alternative I could be using?
1247562433 J * uva bno@118-160-174-128.dynamic.hinet.net
1247563038 M * arachnist first, vserver isn't virtualization
1247563123 Q * imcsk8 Quit: This computer has gone to sleep
1247563475 M * Swordsman well, something similar.
1247563654 J * BenG ~bengreen@94-169-110-10.cable.ubr22.aztw.blueyonder.co.uk
1247563740 M * Swordsman though if that's the case, then the first sentence on the front page of the main page is pretty misleading
1247563961 J * ktwilight_ ~keliew@62.85-240-81.adsl-dyn.isp.belgacom.be
1247563988 M * Swordsman anyhow, I pretty much just wanted something that would isolate users on my server so they can't screw things up
1247564177 Q * mxs Ping timeout: 480 seconds
1247564366 Q * ktwilight Ping timeout: 480 seconds
1247564546 J * ktwilight__ ~keliew@77.6-240-81.adsl-dyn.isp.belgacom.be
1247564546 Q * ktwilight_ Read error: Connection reset by peer
1247565092 J * Swords2 ~kohii@pool-71-112-25-59.sttlwa.dsl-w.verizon.net
1247565170 M * ard Swordsman : virtualization is a state of mind.
1247565202 M * ard running multiple website from 1 apache and a single ip is already virtualization
1247565253 M * ard virtual machines are a kind of virtualization
1247565284 M * ard actually OOP is a state of mind. virtualization is just virtualizing ;-).
1247565516 Q * Swordsman Ping timeout: 480 seconds
1247565742 M * puck Hey, I want to through the 2.3 vserver patch onto a Debian Lenny box.  But keep it as close to stock as possible.  Is patching against 2.6.26 okay?
1247566802 N * Bertl_zZ Bertl
1247566811 M * Bertl morning folks!
1247566889 M * Bertl Swords2: for your purpose the Linux-VServer virtualization/isolation sounds like a perfect match
1247566941 M * Bertl puck: 2.6.26 mainline and all Linux-VServer patches for that kernel can be considered broken, so if you want a working kernel, go for 2.6.27.x or 2.6.22.x 
1247566959 M * Bertl (note that 2.6.26 is also unmaintained)
1247567135 M * fback Bertl: you're maintaining 2.3 series for 2.6.22.x?
1247567186 M * puck Bertl: damn, thought so.
1247567194 M * puck Okay, I'll jump to 2.6.27.x or beyond
1247567201 M * Bertl 2.6.22 is kind of maintained (i.e. it still gets bug fixes if there are reports)
1247567707 J * mrfree ~mrfree@host1-89-static.40-88-b.business.telecomitalia.it
1247568249 M * puck Bertl: Would you recommend 2.6.27.x for the 2.3 patch?
1247568291 M * pmjdebruijn Bertl: no, 2.6.22.x was dropped a long time ago
1247568306 M * pmjdebruijn I think .19 was announced to be the last
1247568323 M * pmjdebruijn but it has been maintained longer than normal kernels
1247568417 M * Bertl I was talking about the Linux-VServer patch :)
1247568447 M * pmjdebruijn oh
1247568447 M * pmjdebruijn :s
1247568458 M * Bertl from mainline, 2.6.27.x is the one still being maintained :)
1247568501 M * pmjdebruijn I know
1247568522 M * pmjdebruijn I think 2.6.16.62 is still maintained as well, but it will be unmaintained very soon
1247568537 M * puck cool
1247568578 A * pmjdebruijn loves the -stable kernels
1247569595 M * Bertl puck: 2.6.27.x should be fine
1247570761 Q * derjohn_foo Ping timeout: 480 seconds
1247570907 Q * mrfree Quit: Leaving
1247571628 Q * scientes_ Ping timeout: 480 seconds
1247571692 M * Bertl ard: can't reproduce the issue ... I'm running your test programin a loop here (on 2.6.30.1-vs2.3.0.36.14-pre3) and absolutely nothing unusual happens ...
1247571970 Q * kolorafa Quit: kolorafa will be back
1247572103 Q * balbir_ Read error: Connection reset by peer
1247572393 Q * BenG Quit: I Leave
1247572670 J * BenG ~bengreen@94-169-110-10.cable.ubr22.aztw.blueyonder.co.uk
1247572701 J * doener ~doener@i59F54B41.versanet.de
1247572806 Q * doener_ Ping timeout: 480 seconds
1247572927 Q * Piet__ Remote host closed the connection
1247572993 J * Piet__ ~piet@659AAA4P5.tor-irc.dnsbl.oftc.net
1247572997 J * balbir_ ~balbir@122.172.45.217
1247573759 N * Piet__ Piet
1247573799 M * Bertl ard: anyway, I fixed a few potential issues and reinstated the vroot stuff in pre4, please retest with this version and let me know if you still can recreate the issue on your setup
1247575026 J * docelic__ ~docelic@78.134.204.215
1247575113 J * ViRUS ~mp@p579B5F93.dip.t-dialin.net
1247575421 Q * docelic_ Ping timeout: 480 seconds
1247576043 M * vasko Bertl: speaking of 2.6.30.1-vs2.3.0.36.14-pre3 problems -- i've give it a try on my workstation and kde4 silently failed to start, put me back to kdm. had no time to experimet so i've recompiled 2.6.30.1 with the same config but without vs patch and it works ok as before. Later that day did the same at home with the same result, nothing in dmesg,xorg log or ~/.xsession-errors
1247576871 M * Bertl okay, then please try the pre4 too, and let me know
1247576886 Q * BenG Quit: I Leave
1247578274 Q * Piet Remote host closed the connection
1247578443 J * Piet ~piet@659AAA4TI.tor-irc.dnsbl.oftc.net
1247579723 Q * fback Ping timeout: 480 seconds
1247580441 M * FIChTe bertl
1247580458 M * FIChTe pre4 and debian 2.6.30-1 works so far
1247580810 M * FIChTe on amd64 :)
1247581165 J * geb ~geb@AOrleans-253-1-68-94.w92-140.abo.wanadoo.fr
1247581165 J * dave0 ~dmo@home.dmo.ca
1247581201 M * geb hi
1247581270 M * dave0 Hello.  Are there any known issues with the vserver support in the Debian lenny kernel?
1247581277 M * dave0 I'm seeing weird guest loopback behaviour
1247581314 J * fback ~fback@pc-nest01-254.sikornik.net
1247581575 M * dave0 anyway... a 127.x.y.1 is created for each vserver, but it doesn't get used
1247581644 M * geb what do you mean by doesn't get used ?
1247581663 M * geb there is some know issue, the kernel and the patch are a bit old
1247581697 M * geb for example you'll have problemes with cpu limits and with the barrier if you change kernel after creating some guests
1247581734 M * dave0 127.0.0.1 is being rewritten to the IP I've used in interfaces/0/ip
1247581746 M * dave0 which is not what I'd expect at all
1247581807 M * dave0 nflags are set appropriately, as far as I can tell: lback_remap,hide_netif,hide_lback,state_admin
1247581862 M * geb the loopback will work by default, try to remove those flags expecialy lback_remap  and hide_lback 
1247582147 M * daniel_hozac dave0: are those the only flags?
1247582159 M * daniel_hozac dave0: i.e. all which are returned from nattribute --get?
1247582173 M * dave0 ues
1247582175 M * dave0 yes
1247582193 M * Bertl dave0: if your kernel has AUTO_SINGLE_IP enabled, you want to disable it with ~single_ip
1247582223 M * Bertl dave0: also, yes, there are known issues with the debian kernels, specifically the 2.6.26.x ones
1247582266 M * dave0 Bertl: ~single_ip is in nflags for that vserver
1247582309 M * dave0 I'm rebuilding a 2.6.30.1 from upstream, with patch, but my last boot of it panicked in ext3 code... what's the most stable kernel to use with the devel patch?
1247582323 M * Bertl daniel_hozac: btw, the cryptic save_ctxinfo issue was a missing /bin/env
1247582345 M * Bertl dave0: patch-2.6.30.1-vs2.3.0.36.14-pre4.diff
1247582363 M * dave0 oh, there's a pre4?  Crap.
1247582365 M * Bertl dave0: 2.6.27.x and 2.6.29.x should be fine
1247582374 M * nox s.o from westcoast US online?
1247582698 Q * ghislainocfs2 Quit: Leaving.
1247582854 M * daniel_hozac nox: kinda early for that.
1247582871 Q * geb Ping timeout: 480 seconds
1247582883 J * geb ~geb@earth.gebura.eu.org
1247582926 M * Bertl FIChTe: great!
1247582931 M * Bertl off for now ... bbl
1247582940 N * Bertl Bertl_oO
1247582958 M * nox daniel_hozac: worth a try :)
1247584337 J * mxs mxs@p4FCCAA24.dip.t-dialin.net
1247584514 M * dave0 geb: removing lback_remap and hide_lback doesn't help (nor would I expect it to). 
1247585459 J * dowdle ~dowdle@scott.coe.montana.edu
1247585679 N * ensc|w Guest1126
1247585686 J * ensc|w ~ensc@www.sigma-chemnitz.de
1247585697 Q * Guest1126 Read error: No route to host
1247585706 Q * FireEgl Remote host closed the connection
1247585718 Q * dowdle Remote host closed the connection
1247585837 Q * esa Quit: Coyote finally caught me
1247586608 J * FireEgl Proteus@WTF.4.1.0.c.0.7.4.0.1.0.0.2.ip6.arpa
1247586650 M * dave0 wow, that was... obscure
1247586680 M * dave0 I figured out why 127.0.0.1 wasn't being mapped to my 127.x.y.1 address: I didn't have an interfaces/0/prefix
1247586756 M * dave0 does anyone know why that happens?
1247587764 J * bonbons ~bonbons@2001:960:7ab:0:2c0:9fff:fe2d:39d
1247587764 Q * FireEgl Remote host closed the connection
1247587770 Q * davidkarban Quit: Ex-Chat
1247587785 J * fback_ fback@red.fback.net
1247587879 J * imcsk8 ~ichavero@189.155.83.205
1247587902 Q * fback Ping timeout: 480 seconds
1247588344 Q * imcsk8 Quit: This computer has gone to sleep
1247588540 N * julius_ Wophon
1247588619 J * FireEgl Proteus@Sebastian.Atlantica.CJB.Net
1247590951 N * fback_ fback
1247591021 N * Bertl_oO Bertl
1247591082 M * Bertl dave0: why what happens? why you didn't configure the prefix properly?
1247591145 M * dave0 Bertl: 'vserver build' didn't configure it for me, and I didn't bother adding it manually
1247591170 M * Bertl what util-vserver version do you have?
1247591174 M * dave0 so, without the prefix, 127.0.0.1 was always rewritten to my guest's interfaces/0 IP address
1247591200 M * dave0 0.30.216~r2772-6 from debian lenny
1247591212 M * Bertl and your build line was?
1247591225 M * dave0 ... lost to the sands of time :(
1247591228 J * gate_keeper_ ~gk@92.53.16.197
1247591278 M * dave0 anyway, the autogenerated lback address never gets used if there's no prefix on the 0 interface
1247591326 M * dave0 verified on 2.6.30.1 + vs2.3.0.36.14-pre4, and on whatever abomination Debian has patched into 2.6.26
1247591352 M * Bertl if the kernel gets assigned <ip>/0 then it is the proper behaviour, as this is the IP to be used for anyhting
1247591420 M * dave0 Maybe defaulting the prefix to 0 if unspecified is a bad idea?
1247591427 M * dave0 at least, it should generate a warning
1247591439 M * Bertl but IIRC, util-vserver complains about such a setup, but daniel_hozac should have the details
1247591455 M * Bertl (that's why the build line would have been interesting)
1247591515 M * Bertl i.e. either prefix or netmask need to be set, otherwise you get a warning
1247591691 M * dave0 http://paste.linux-vserver.org/13122
1247591713 M * dave0 so -m skeleton at least doesn't warn
1247591743 M * Bertl IIRC, the warning is on guest startup
1247591780 M * Bertl (but it might make sense to add a warning to the build part too)
1247592015 N * DoberMann[ZZZzzz] DoberMann
1247592031 M * dave0 Bertl: yeah, I definitely didn't see any warnings at startup
1247592075 M * dave0 there was one at shutdown, though: Warning: Executing wildcard deletion to stay compatible with old scripts
1247592105 M * dave0 while trying to silence that one by setting a prefix I discovered that it fixed my 127.0.0.1 problem as well
1247592185 A * dave0 debootstraps another one to check for warnings
1247592280 M * Bertl okay, please file a bug report to util-vserver (feature request) that this should be warned on at build time (and startup)
1247592669 J * dowdle ~dowdle@scott.coe.montana.edu
1247592969 Q * pmenier Quit: Konversation terminated!
1247593928 M * dave0 Bertl: the savannah bugtracker, or is there a better way?
1247594095 M * Bertl nah, savannah is fine
1247594171 M * dave0 meh... need to create a savannah account to file bugs there
1247595675 J * imcsk8 ~ichavero@189.155.83.205
1247595839 J * Pazzo ~ugelt@reserved-225136.rol.raiffeisen.net
1247598253 Q * FireEgl Ping timeout: 480 seconds
1247598277 P * miguelzinho Leaving
1247598815 J * FireEgl FireEgl@173-16-9-10.client.mchsi.com
1247599738 J * ghislainocfs2 ~Ghislain@adsl2.aqueos.com
1247600504 M * ard :-(
1247600522 M * ard EIP is at ext3_has_free_blocks+0x9/0x60
1247600535 M * Bertl with pre4?
1247600536 M * ard BUG: unable to handle kernel paging request at 0000ef5b
1247600536 M * ard trippeh: [<c0227419>] ext3_has_free_blocks+0x9/0x60
1247600541 M * ard nope, not yet :-)
1247600545 M * ard I will now try that
1247600549 M * Bertl please do so :)
1247600571 M * ard this is the 32bit system at home, so it takes a while :-(
1247600593 M * Bertl about 5min for compile, if you cleanup the config :)
1247600660 M * ard well, then I will probably not be able to use any of my usb devices ;-)
1247600668 M * ard compile is still done on a server
1247600680 M * ard but this system also needs fglrx :-(
1247600692 M * ard (my card is too old for open source drivers)
1247600762 M * ard kernel almost prepped for compilation...
1247600787 M * ard cachefs also doesn't work very well on 2.6.30.1
1247600795 M * ard with or without vserver ;-)
1247600860 M * dave0 Bertl: that's what I had with pre3 earlier today
1247600889 M * ard dave0: cachefs?
1247600908 M * dave0 ard: no, your ext3_has_free_blocks issue
1247600915 M * ard ah :-)
1247600916 M * dave0 pre4 is working fine so far
1247600965 M * ard I first assumed a problem with acls, but in the end it must have something to do with caching and late block allocation
1247601128 M * ard http://stats.kwaak.net/munin/dc0/algapi.dc0-vsmemory.html will change in 5 minutes to a stack of RSS
1247601361 Q * imcsk8 Quit: This computer has gone to sleep
1247601447 A * ard meant http://stats.kwaak.net/munin/dc0/blowfish.dc0-vsmemory.html
1247601692 M * Bertl  yes, I fixed a bug in the balloc code (ext3)
1247601719 M * ard w0000t
1247601899 M * ard almost finished
1247601906 M * ard kernel is finished, now 3d drivers
1247602499 M * ard for now the bug is not reproducible
1247602500 M * ard w000t
1247602528 M * ard I assume that will also fix the 64 bit versions
1247602774 M * Bertl the kernel doesn't make much difference between 32 and 64bit nowadays
1247602797 M * ard well, the 64 bit said ENOSPC, and the 32 bit oopsed :-)
1247602828 M * ard although the 32bit was ext3 loop mounted on an ext4 fs
1247603410 M * ard < -     if (!ext3_has_free_blocks(sbi)) {
1247603410 M * ard < +     if (!ext3_has_free_blocks(sb)) {
1247603410 M * ard <               *errp = -ENOSPC;
1247603418 M * ard I can understand that fixed it :-)
1247603689 M * ard but, eh, you fixed a bug in plain 2.6.30.1?
1247603862 M * Bertl nope, in the Linux-VServer patch
1247604012 M * ard ah...
1247604028 M * ard reading a diff -u of 2 patch files is a little bit hard...
1247604033 M * ard but I see it now :-)
1247604217 Q * bonbons Quit: Leaving
1247604367 J * Kmos ~gothicx@kmos.user.oftc.net
1247604468 M * ard write(3, "\0\0\0\0\0\0\0\0\3309\360\230\37\177\0\0\1\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\1"..., 117) = 117
1247604470 M * ard it works :-)
1247604479 M * Bertl good :)
1247604716 M * ard on to the next thing
1247604721 M * ard will cachefs work :-)
1247604731 M * mnemoc Bertl: hi, if you find a minute, may you make a 2.3.0.36.6 patch for 2.6.27.26? :) it's only the first hunk of drivers/md/dm.c that fails from .25's patch
1247604771 M * ard (/me gained 2MB/s read speed from the local nfs server today. From 63MB/s to 65MB/s uncached...)
1247604921 Q * FireEgl Ping timeout: 480 seconds
1247605518 J * FireEgl FireEgl@173-16-9-10.client.mchsi.com
1247605655 M * ard weird... /me created a 10G file on ext4 with dd, and it uses 0x1400008 blocks.... 8 more than necessary on an extent based filesystem
1247605997 J * imcsk8 ~ichavero@148.229.1.11
1247606150 M * ard ah.... cachefs works on ext3 but not on ext4
1247606558 N * DoberMann DoberMann[ZZZzzz]
1247607322 M * Bertl mnemoc: the change in 2.6.27.26 to dm.c is bogus
1247607423 M * ard Bertl : it magically also fixed some weird blanking issues I had with fglrx ...
1247607543 A * ard only doesn't see any relation
1247607568 M * ard because I also had blanking problems with 2.6.28
1247607571 M * Bertl check the fglrx source code :)
1247607589 M * ard :-(
1247607624 M * ard too old, it's an r420, and there are open source drivers starting from r500
1247607634 M * Bertl maybe it shows some blanking problems when you do not have network access (i.e. the DDoS client cannot work properly :)
1247607635 N * dave0 dave0gone
1247607683 M * ard But then again, maybe this latest patch also cures my skinproblems!
1247607684 M * ard :-)
1247609701 Q * Piet Ping timeout: 480 seconds
1247609860 J * Piet ~piet@659AAA5IE.tor-irc.dnsbl.oftc.net
1247610315 Q * imcsk8 Quit: This computer has gone to sleep
1247611340 Q * docelic__ Quit: http://www.spinlocksolutions.com/
1247611755 Q * Pazzo Quit: Ex-Chat
1247611859 J * thierryp ~thierry@home.parmentelat.net
1247611873 Q * thierryp 
1247612358 Q * Kmos Quit: return unless user.signoff?
1247612494 Q * ghislainocfs2 Quit: Leaving.
1247612512 Q * dowdle Remote host closed the connection
1247614273 M * Bertl mnemoc: uploaded a patch for 2.6.27.26 (please test and report back on the dm stuff :)
1247614562 J * ousado ~johnny@p5B3C2E43.dip0.t-ipconnect.de