On 14 September 2010 10:00, JL <lvs@xxxxxxxx> wrote:
>> Then might I recommend an Occam's Roazor approach to this? Compile a
>> number of kernels from the one which worked up to the one which doesn't.
>> Reboot the backup; test; if it doesn't happen then you know the change
>> cam later than the kernel you're running.
> I intend to do that.
126.96.36.199 - OK
188.8.131.52 - OK
2.6.28 - Fail
184.108.40.206 - Fail
220.127.116.11 w/ Classic RCU - Fail
18.104.22.168 w/ Tree RCU - Fail
22.214.171.124 - Fail
126.96.36.199 - Fail
I'm convinced the problem was introduced in 2.6.28.
I still believe this is somehow related to the insertion of connection
entries received from the master into some in-memory table on the
Please read the documentation before posting - it's available at:
LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
or go to http://lists.graemef.net/mailman/listinfo/lvs-users