invalid swap state

[GoogleCodeExporter]

What is the expected output? What do you see instead?
/usr/local/squid/var/logs/cache.log:2010/03/02 14:23:06| WARNING: 1 invalid 
swap log entries 
found
/usr/local/squid/var/logs/cache.log:2010/03/02 14:23:06| WARNING: 10 invalid 
swap log 
entries found
/usr/local/squid/var/logs/cache.log:2010/03/02 14:23:06| WARNING: 100 invalid 
swap log 
entries found
/usr/local/squid/var/logs/cache.log.1:2010/02/25 16:51:59| WARNING: 1 invalid 
swap log 
entries found
/usr/local/squid/var/logs/cache.log.1:2010/02/25 16:51:59| WARNING: 10 invalid 
swap log 
entries found
/usr/local/squid/var/logs/cache.log.1:2010/02/25 16:51:59| WARNING: 100 invalid 
swap log 
entries found
/usr/local/squid/var/logs/cache.log.1:2010/02/25 16:55:08| WARNING: 1 invalid 
swap log 
entries found
/usr/local/squid/var/logs/cache.log.1:2010/02/25 16:55:08| WARNING: 10 invalid 
swap log 
entries found
/usr/local/squid/var/logs/cache.log.1:2010/02/25 17:07:21| WARNING: 1 invalid 
swap log 
entries found
/usr/local/squid/var/logs/cache.log.1:2010/02/25 17:07:21| WARNING: 10 invalid 
swap log 
entries found
/usr/local/squid/var/logs/cache.log.1:2010/02/25 17:07:21| WARNING: 100 invalid 
swap log 
entries found
/usr/local/squid/var/logs/cache.log.1:2010/02/25 18:13:11| WARNING: 1 invalid 
swap log 
entries found
/usr/local/squid/var/logs/cache.log.1:2010/02/25 18:13:11| WARNING: 10 invalid 
swap log 
entries found
/usr/local/squid/var/logs/cache.log.1:2010/02/25 18:13:11| WARNING: 100 invalid 
swap log 
entries found
/usr/local/squid/var/logs/cache.log.1:2010/02/25 22:34:38| WARNING: 1 invalid 
swap log 
entries found
/usr/local/squid/var/logs/cache.log.1:2010/02/25 22:34:38| WARNING: 10 invalid 
swap log 
entries found
/usr/local/squid/var/logs/cache.log.1:2010/02/25 22:34:38| WARNING: 100 invalid 
swap log 
entries found
/usr/local/squid/var/logs/cache.log.1:2010/02/25 22:37:19| WARNING: 1 invalid 
swap log 
entries found
/usr/local/squid/var/logs/cache.log.1:2010/02/25 22:37:19| WARNING: 10 invalid 
swap log 
entries found
/usr/local/squid/var/logs/cache.log.1:2010/02/27 19:09:08| WARNING: 1 invalid 
swap log 
entries found
/usr/local/squid/var/logs/cache.log.1:2010/02/27 19:09:08| WARNING: 10 invalid 
swap log 
entries found
/usr/local/squid/var/logs/cache.log.1:2010/02/27 19:09:08| WARNING: 100 invalid 
swap log 
entries found
/usr/local/squid/var/logs/cache.log.1:2010/03/01 13:48:06| WARNING: 1 invalid 
swap log 
entries found
/usr/local/squid/var/logs/cache.log.1:2010/03/01 13:48:06| WARNING: 10 invalid 
swap log 
entries found
/usr/local/squid/var/logs/cache.log.1:2010/03/01 13:48:06| WARNING: 100 invalid 
swap log 
entries found
/usr/local/squid/var/logs/cache.log.1:2010/03/01 23:24:18| WARNING: 1 invalid 
swap log 
entries found

What version of the product are you using? On what operating system?
LUSCA_HEAD

Debian 5.0 amd64

Please provide any additional information below.

Original issue reported on code.google.com by kris%amy...@gtempaccount.com on 2 Mar 2010 at 4:29

[GoogleCodeExporter]

I've figured this out. The helper code child sends a "hello" string to the main 
process. Lusca reads 32 bytes for 
the helper in case more data is sent.

The problem is that the helper code child sends "hello" and then exec()'s the 
process, which may start running 
immediately. That means the first bit of data written by the ufs_rebuild helper 
is being eaten by the "hello" read 
of 32 bytes by the main Lusca process.

So that's the problem. Now, the solution..

Original comment by adrian.c...@gmail.com on 23 Mar 2010 at 9:17

• Changed state: Accepted
• Added labels: Priority-Critical, Version-Head
• Removed labels: Priority-Medium, Version-1.0

[GoogleCodeExporter]

Hopefully fixed in r14477!

Original comment by adrian.c...@gmail.com on 23 Mar 2010 at 12:41

[GoogleCodeExporter]

Please test LUSCA_HEAD from SVN and let me know if you have any further 
problems!

Original comment by adrian.c...@gmail.com on 23 Mar 2010 at 12:45

• Changed state: Fixed