1269130356 Q * ntrs Ping timeout: 480 seconds 1269130399 N * DoberMann[PullA] DoberMann[ZZZzzz] 1269133091 Q * ghislain1 Quit: Leaving. 1269134182 Q * Romster Ping timeout: 480 seconds 1269134342 Q * MeCooL Ping timeout: 480 seconds 1269135733 J * Romster ~romster@202.168.100.149.dynamic.rev.eftel.com 1269136282 Q * urbee Ping timeout: 480 seconds 1269138841 Q * Romster Ping timeout: 480 seconds 1269140420 J * Romster ~romster@202.168.100.149.dynamic.rev.eftel.com 1269140909 J * undefined ~undefined@adsl-68-93-97-69.dsl.rcsntx.swbell.net 1269141969 J * derjohn_foo ~aj@pD95FC8E0.dip.t-dialin.net 1269142035 M * undefined i'm getting strange disk accounting 1269142074 M * undefined well, besides testfs.sh-0.23 failing 1269142090 M * Bertl kernel/patch and util-vserver version? 1269142139 M * undefined i'm testing 2.6.32.10-vs2.3.0.36.29.2 & 0.30.216-pre2841 1269142202 M * Bertl okay, what 'stange' accounting do you see? 1269142209 M * Bertl *strange even 1269142290 M * undefined usually i use 0.30.216-pre2772, and that worked fine with 2.6.27.y, but i'm trying 2.6.32.y and that util-vserver version worked fine except for the vdlimits so i upgraded to this newer version that i had compiled previously to test a prior problem 1269142313 M * undefined vdlimit says i have one inode used 1269142318 M * Bertl well, 2772 is too old for 2.6.32 kernels 1269142336 M * undefined so i touch 4 files 1269142357 M * undefined on touching the 5th file, "Disk quota exceeded" 1269142373 M * undefined but vdlimit says i've only used 4 inodes 1269142385 Q * derjohn_mob Ping timeout: 480 seconds 1269142388 M * undefined so i try touching the 5th file again and it works 1269142398 M * Bertl and your limit is 5 inodes, yes? 1269142413 M * undefined yes, inodes_total=5 1269142420 M * undefined (just for testing) 1269142427 M * Bertl just checking 1269142470 M * Bertl after that, the limit has been reached and everything is fine or? 1269142516 M * undefined nope, it gets weirder after that 1269142524 M * Bertl okay :) 1269142550 M * undefined it appears that every time i run vdlimit, to see the stats, the inodes_used decreases by one 1269142579 M * undefined well, every time i hit the limit, the inodes_used decreases by one 1269142675 M * Bertl okay, that definitely sounds like a bug 1269142685 M * Bertl what filesystem do you use? 1269142691 M * undefined ext3 1269142713 M * Bertl could you mount it as ext2 for a test? 1269142846 M * undefined yeah 1269142850 M * undefined http://paste.linux-vserver.org/14842 1269142866 M * undefined hopefully that better explains what i'm seeing 1269143049 M * undefined ext2 generates same behavior 1269143286 M * Bertl okay, that basically a good sign 1269143312 M * Bertl means that it is not some kind of reservation oddity (which would be harder to track down) 1269143371 Q * Romster Ping timeout: 480 seconds 1269143628 M * Bertl does your kernel have Linux-VServer debugging enabled? 1269143792 M * undefined i don't think so 1269143806 M * undefined # CONFIG_VSERVER_DEBUG is not set 1269143876 M * Bertl okay, let me see if I can recreate it here 1269143889 M * undefined i can recompile if necessary; it's a test machine 1269144066 J * SauLus_ ~SauLus@d003041.adsl.hansenet.de 1269144141 M * Bertl wouldn't hurt, in case I cannot 1269144314 J * Romster ~romster@202.168.100.149.dynamic.rev.eftel.com 1269144347 M * Bertl okay, I can reproduce the inode count decrements on limit hit here 1269144371 M * Bertl I cannot reproduce any change when using vdlimit 1269144475 Q * SauLus Ping timeout: 480 seconds 1269144475 N * SauLus_ SauLus 1269144491 M * undefined yeah, i only noticed the decrement by using vdlimit (trying to understand testfs.sh) 1269144519 M * undefined but i tested it further and realized it was when hitting the limit (as seen in the paste) 1269144562 M * Bertl ah, okay, good, so that I can reproduce, looking into it right now 1269144611 M * undefined and i don't even know if this is related to the failure i'm seeing in testfs.sh (tests 208 & 233) 1269144626 M * undefined i was just trying to figure out what testfs.sh did and stumbled upon this 1269144711 M * Bertl well, it's definitely a bug, so good that you found it 1269145261 M * Bertl okay, I think I know what the problem is .. *testing* 1269145461 M * undefined it appears that test 208 was trying to tell me what i discovered on my own walking through to test 207 1269145483 M * undefined but "verify 300: 2 ~ 1" wasn't intuitive to me 1269145484 M * undefined ;) 1269145562 M * undefined and appears that the failure of test 233 is probably related, as it is a do_dlimit_verify immediately following a "touch: cannot touch `/mnt/cow-300-9': Disk quota exceeded" 1269145691 M * Bertl yeah, the tests are not very self explanatory, feel free to improve them :) 1269145847 M * undefined i added comments the last time i submitted a patch to testfs.sh, but thankfully no patch to testfs.sh is needed this time ;) 1269146311 M * Bertl http://vserver.13thfloor.at/ExperimentalT/delta-dlimit-fix02.diff 1269146322 M * Bertl this should fix the issue for all filesystems 1269146516 M * undefined i'm rebuilding now, will test it tonight or tomorrow, and let you know the results 1269146527 M * Bertl excellent! thanks in advance! 1269146538 M * undefined thank you for the fix! 1269146545 M * Bertl you're welcome! 1269147121 M * Bertl off to bed now ... have a good one everyone! 1269147126 N * Bertl Bertl_zZ 1269147807 Q * Romster Ping timeout: 480 seconds 1269147920 J * Romster ~romster@202.168.100.149.dynamic.rev.eftel.com 1269151609 Q * Romster Remote host closed the connection 1269153195 Q * theocrite Ping timeout: 480 seconds 1269153277 J * theocrite ~Hubert@kim.theocrite.org 1269155108 J * ghislain ~AQUEOS@adsl2.aqueos.com 1269156424 J * MeCooL mecool@94.129.171.169 1269157015 J * Romster ~romster@202.168.100.149.dynamic.rev.eftel.com 1269157468 J * ntrs ~ntrs@77.29.197.187 1269157505 M * undefined Bertl_zZ: finally got around to installing the kernel image with the dlimit fix and testfs.sh-0.23 no longer fails on tests 208 and 233 (meaning you at least have vdlimit fooled ;-)) and it worked fine manually (tried to exceed the inode limit twice in a row irregardless of vdlimit output) 1269157569 P * undefined 1269159852 Q * ktwilight_ Ping timeout: 480 seconds 1269160713 Q * Bushmills Remote host closed the connection 1269160944 J * hijacker ~hijacker@87-126-142-51.btc-net.bg 1269161409 J * petzsch ~markus@p4FF44966.dip.t-dialin.net 1269161557 Q * ntrs Ping timeout: 480 seconds 1269162124 Q * Loki|muh Remote host closed the connection 1269162387 J * ktwilight ~keliew@91.180.48.204 1269164084 J * cluk ~cluk@p5B17C707.dip.t-dialin.net 1269164470 Q * derjohn_foo Ping timeout: 480 seconds 1269164568 J * Bushmills ~l@scarydevilmonastery.net 1269165320 J * bonbons ~bonbons@2001:960:7ab:0:2c0:9fff:fe2d:39d 1269165493 Q * nou Ping timeout: 480 seconds 1269165740 Q * Piet Remote host closed the connection 1269166824 J * Piet ~Piet__@04ZAAA689.tor-irc.dnsbl.oftc.net 1269167251 J * Loki|muh ~loki@satanix.de 1269168911 J * nou Chaton@2001:6f8:328:bbc:6666:6667:: 1269168919 Q * nou 1269168985 J * nou Chaton@causse.larzac.fr.eu.org 1269170222 J * ghislain1 ~AQUEOS@adsl2.aqueos.com 1269170382 Q * infowolfe Server closed connection 1269170395 J * infowolfe ~infowolfe@c-71-236-152-35.hsd1.or.comcast.net 1269170532 Q * ghislain Ping timeout: 480 seconds 1269171255 Q * petzsch Quit: Leaving. 1269171687 J * derjohn_foo ~aj@e180194171.adsl.alicedsl.de 1269172782 Q * Snow-Man Server closed connection 1269172783 J * Snow-Man ~sfrost@tamriel.snowman.net 1269172822 J * petzsch ~markus@p4FF44966.dip.t-dialin.net 1269172898 J * dna ~dna@p54BC95CF.dip0.t-ipconnect.de 1269176470 N * Bertl_zZ Bertl 1269176477 M * Bertl morning folks! 1269176705 Q * hijacker Quit: Leaving 1269178803 J * ntrs ~ntrs@77.28.61.168 1269178857 Q * petzsch Quit: Leaving. 1269180703 Q * Piet Ping timeout: 480 seconds 1269180733 J * petzsch ~markus@p4FF44966.dip.t-dialin.net 1269181175 M * ghislain1 morning 1269181215 M * ghislain1 hum i have a network issue on a guest, i cannot reach the net. One guest is ok, the other is not, strange 1269181295 M * Bertl try with ping -I www.google.com on the host 1269181315 M * Bertl (try with both guest IPs :) 1269181348 M * ghislain1 it works 1269181353 M * ghislain1 for both 1269181362 M * Bertl okay, then check the resolv.conf in both guests 1269181415 M * Bertl if that is fine too, double check that the guest has the correct IP assigned (and not a slightly different one :) 1269181431 M * Bertl (/proc/virtnet//*) 1269181673 M * ghislain1 humm seems there is a SLIGHT difference ;) 1269181684 M * ghislain1 but very SLIGHT ;p 1269181844 M * Bertl hehe :) 1269181884 Q * ktwilight Remote host closed the connection 1269181967 J * ktwilight ~keliew@91.180.48.204 1269182482 Q * ktwilight Ping timeout: 480 seconds 1269182617 M * ghislain1 this the DoH! effect 1269182636 M * Bertl not really uncommon here as you probably know :) 1269182716 J * Piet ~Piet__@04ZAAA7EW.tor-irc.dnsbl.oftc.net 1269182870 Q * dna Ping timeout: 480 seconds 1269183127 J * dna ~dna@p54BC95CF.dip0.t-ipconnect.de 1269183827 Q * derjohn_foo Read error: Connection timed out 1269183852 J * derjohn_foo ~aj@e180194171.adsl.alicedsl.de 1269186653 Q * Piet Ping timeout: 480 seconds 1269187427 J * Piet ~Piet__@04ZAAA7F9.tor-irc.dnsbl.oftc.net 1269188143 J * fleischergesell ~fleischer@dslb-092-072-238-188.pools.arcor-ip.net 1269188203 M * fleischergesell How can I modify the list of files that vhashify excludes? 1269188317 M * Bertl check out the flower page, there is a config path for that 1269188588 M * fleischergesell Which config path is being used if there is no "exlude" file in /apps/vunify/ nor in .defaults/apps/vunify/? 1269188817 M * Bertl it is in the syntax 1269188834 M * Bertl i.e. check out the default, it should be pretty obvious 1269189099 Q * Bushmills Remote host closed the connection 1269189382 J * Bushmills ~l@scarydevilmonastery.net 1269191112 Q * petzsch Quit: Leaving. 1269191583 Q * Romster Remote host closed the connection 1269191866 J * petzsch ~markus@p4FF44966.dip.t-dialin.net 1269192644 Q * derjohn_foo Read error: Connection timed out 1269192718 J * derjohn_foo ~aj@e180194171.adsl.alicedsl.de 1269193214 Q * petzsch Read error: Connection reset by peer 1269193215 J * petzsch ~markus@p4FF44966.dip.t-dialin.net 1269193946 Q * nkukard Quit: Leaving 1269194050 Q * cluk Ping timeout: 480 seconds 1269194202 Q * derjohn_foo Read error: Connection timed out 1269194232 J * derjohn_foo ~aj@e180194171.adsl.alicedsl.de 1269194318 J * cluk ~cluk@p5B17C707.dip.t-dialin.net 1269195735 M * geb hi :) 1269195765 M * geb Bertl, is the 2.6.33 ~patch stable or should we wait a bit more for using it ? 1269195774 M * geb ~stable not ~patch :) 1269195795 M * Bertl it is experimental, the last stable patch is for 2.6.22 1269195990 M * geb yeah, i know, that's not the question, is the patch as stable as for example the 2.6.32 one ? :) 1269196159 M * geb ... or should we wait a bit more for starting to use it ? 1269196204 M * Bertl yep, definitely as stable as 2.6.32 1269196462 M * geb 'k, i will give a try with uml so :) 1269196489 M * geb (there is a very annoying bug in uml with 2.6.32 : http://www.mail-archive.com/user-mode-linux-user@lists.sourceforge.net/msg06776.html ) 1269196660 M * geb i found something a bit strange with ipv6 prefix: http://paste.linux-vserver.org/14843 1269196731 M * geb the prefix seems to be ignored, and a /128 is created, it doesn't hurt so much, except that it create a /128 route per vserver 1269196754 M * geb dunno if it is userland (and so that i have to try with a recent vserver) or kernel land 1269196774 M * geb with a recent recent util-vserver , sorry 1269196853 M * geb any opinion ? :) 1269196955 M * geb http://paste.linux-vserver.org/14845 ( show the routes ) 1269197110 M * Bertl bonbons is the ipv6 expert :) 1269197400 M * bonbons geb: looks like userland issue (util-vserver?), the kernel side should have no impact on address assignment... 1269197461 M * geb 'k thanks, i will try to test once my vserver on uml will be up 1269197544 M * bonbons geb: also have a look at the contents of /proc/virtnet/$guest/info - interesting to know if the same prefix is set there 1269197604 M * geb http://paste.linux-vserver.org/14846 (bottom) :) 1269197851 M * bonbons geb: so right prefix mentionned to vserver but wrong one used for/by ip/ifconfig when assigning new ipv6 address? 1269197917 M * geb yeah, look something like 1269197922 M * geb looks 1269197978 M * geb i dunno how important it is, i don't think that having a route per vserver, hurt the performances a lot, but maybe it has other implications 1269198002 M * bonbons geb: I guess it might be worth making util-vserver's calls to ip/ifconfig printed out and check state before/after their call 1269198051 M * geb yeah right, but maybe should i test with a recent util vserver before :) 1269198109 M * bonbons that might solve it too 1269198164 M * geb is ben here ? i found a tiny bug on his util-vserver package ? 1269198225 M * geb ( the debian vserver refuse to install if there is a /vservers , for myself i usualy ln -s /var/lib/vservers / , so it is not a problem, and maybe the check is a bit too strict) 1269198475 J * hijacker ~hijacker@87-126-142-51.btc-net.bg 1269198627 Q * fleischergesell Ping timeout: 480 seconds 1269199732 J * nkukard ~nkukard@196.212.73.74 1269199962 J * fleischergesell ~fleischer@dslb-084-063-120-219.pools.arcor-ip.net 1269200454 Q * petzsch Quit: Leaving. 1269200690 J * fleischermeister ~fleischer@dslb-088-077-221-135.pools.arcor-ip.net 1269200691 Q * fleischergesell Ping timeout: 480 seconds 1269201173 Q * fleischermeister Ping timeout: 480 seconds 1269201175 J * fleischergesell ~fleischer@dslb-088-077-221-173.pools.arcor-ip.net 1269201718 J * ktwilight ~keliew@127.176-247-81.adsl-dyn.isp.belgacom.be 1269202392 J * fleischermeister ~fleischer@dslb-084-063-111-254.pools.arcor-ip.net 1269202393 Q * fleischergesell Ping timeout: 480 seconds 1269202637 Q * fleischermeister 1269202637 J * petzsch ~markus@p4FF44966.dip.t-dialin.net 1269203578 Q * ghislain1 Quit: Leaving. 1269206308 Q * petzsch Quit: Leaving. 1269207706 Q * dna Quit: Verlassend 1269208065 Q * hijacker Quit: Leaving 1269208295 J * ghislain ~AQUEOS@adsl2.aqueos.com 1269208389 J * Romster ~romster@202.168.100.149.dynamic.rev.eftel.com 1269209640 Q * ghislain Quit: Leaving. 1269212253 Q * Romster Ping timeout: 480 seconds 1269214063 Q * bonbons Quit: Leaving 1269215574 Q * cluk Quit: Ex-Chat