1432261689 J * zerick ~zerick@irc.quassel.zerick.me
1432264963 J * Bertl_oO herbert@IRC.13thfloor.at
1432264993 M * Bertl_oO off to bed now ... have a good one everyone!
1432265003 N * Bertl_oO Bertl_zZ
1432274227 J * wicope ~wicope@0001fd8a.user.oftc.net
1432276337 Q * derjohn_mob Ping timeout: 480 seconds
1432277773 J * Ghislain ~aqueos@adsl1.aqueos.com
1432278471 J * nikolayK ~nikolay.k@199.91.137.248
1432279847 J * derjohn_mob ~aj@fw.gkh-setu.de
1432283488 Q * derjohn_mob Ping timeout: 480 seconds
1432284061 J * derjohn_mob ~aj@fw.gkh-setu.de
1432284516 M * Ghislain hi
1432284547 M * Ghislain bertl i tried to add the debug code to the 3.18.14 but could not find the  printk in the same file or others in this directory
1432286691 N * Bertl_zZ Bertl
1432286692 M * Bertl morning folks!
1432286950 M * Bertl Ghislain: well, the debug code was for 3.4.* which is very different :)
1432286982 M * Ghislain yes i know i just tried to put it as i was building a new kernel but could not find it
1432286998 M * Ghislain :)
1432287044 Q * wicope Remote host closed the connection
1432288154 M * Ghislain i test testfs that fails some
1432288174 M * Ghislain mount -t ext4 -o rw,tag /dev/vserverpool/testcq /mnt/  work but mounting without tag and then   mount -o remount,rw,tag /mnt/ like in the test fails
1432288221 M * Ghislain [66222.336835] EXT4-fs: dm-7: tagging not permitted on remount.
1432288284 M * Ghislain the test show success but htere is a bunch of error messages. i just put them in the mail to the list
1432288515 M * Bertl yep, remount is not allowed for tagging
1432288533 M * Bertl i.e. that is supposed to fail
1432288559 M * Bertl if you are running testfs.sh, please run it with -vvv and upload the output somewhere
1432291360 Q * Aiken Remote host closed the connection
1432293727 M * Ghislain ok i put only one v i redo with 3
1432294053 M * Ghislain http://pastebin.com/raw.php?i=X5HAMd67
1432294158 M * Bertl looks fine, everything perfect
1432294233 M * Ghislain great then :)
1432295956 Q * derjohn_mob Ping timeout: 480 seconds
1432295960 Q * fstd Remote host closed the connection
1432295971 J * fstd ~fstd@xdsl-87-78-82-16.netcologne.de
1432296928 J * derjohn_mob ~aj@fw.gkh-setu.de
1432298789 Q * derjohn_mob Ping timeout: 480 seconds
1432299864 J * Wermwud ~Wermwud@69-29-150-18.stat.centurytel.net
1432302486 J * wicope ~wicope@0001fd8a.user.oftc.net
1432302949 J * derjohn_mob ~aj@tmo-108-15.customers.d1-online.com
1432303601 Q * bzed Remote host closed the connection
1432305349 N * opuk_ opuk
1432305731 Q * derjohn_mob Ping timeout: 480 seconds
1432306082 J * bzed ~bzed@bzed.netrep.oftc.net
1432312595 Q * hparker Quit: I've fallen off the 'net and can't get up
1432312797 Q * nikolayK Quit: Leaving
1432315255 N * Bertl Bertl_oO
1432318794 J * derjohn_mob ~aj@tmo-108-15.customers.d1-online.com
1432324928 Q * wicope Ping timeout: 480 seconds
1432326476 Q * Defaultti Quit: Quitting.
1432326553 J * Defaultti defaultti@lakka.kapsi.fi
1432328736 J * Aiken ~Aiken@d63f.h.jbmb.net
1432331110 J * benl2 ~benl@officevillage.sonassihosting.com
1432331116 M * benl2 Hey troops
1432331135 M * benl2 Is anyone on here using linux bonds, in active-backup, with arp monitoring enabled
1432331174 M * benl2 I'm seeing curious behaviour that when the arp is sent out for the monitor (to the target IP), that there is also an arp per guest, from itself, to itself
1432331195 M * benl2 This sudden arp flood results in the bonding arp monitor not getting a response in time and marks the interface as down
1432331198 Q * Wermwud Quit: Leaving (Please imagine me slamming the door on my way out)
1432331313 M * benl2 I think populating the arp table with the respective IP in the guest would solve this (given its local). I could write a script to populate /etc/ethers - but I there must be a more elegant approach?
1432331462 M * benl2 Is there a pre/post start/stop script I could hook into?
1432331769 M * daniel_hozac i've only ever used MII monitoring.
1432331792 M * benl2 Yeah, historically I have - but I've got a situation where that won't work
1432332776 M * benl2 Ok, so that's weird. Bringing the interface down and up again stopped it occuring!
1432332786 M * benl2 eg. ifdown bond0; ifup bond0
1432332905 M * daniel_hozac is that because you lost all of your guest IP addresses doing that?
1432332918 M * benl2 No, the guest IPs stayed up
1432332946 M * benl2 I've got net.ipv4.conf.all.promote_secondaries=1
1432332963 P * benl2 
1432332966 J * benl2 ~benl@officevillage.sonassihosting.com
1432332988 M * benl2 ip addr list shows all the interfaces as up
1432335494 Q * Ghislain Quit: Leaving.
1432336214 M * Bertl_oO benl2: could be an arp cache issue
1432339160 Q * fstd Remote host closed the connection
1432339172 J * fstd ~fstd@xdsl-84-44-236-37.netcologne.de