Hi

I just noticed that the object-server and object-auditor are writing a lot of warnings about the posix_fadvise function on both my SAIO setup and a multi-node setup. This happens both on Ubuntu 10.04 and Debian Squeeze when using the 1.3 trunk version of swift. The error log contains a lot of lines like this:

Apr 4 14:56:04 blazer1 object-server STDOUT: WARNING:root:posix_fadvise(16, 0, 112, 4) -> 22 (txn: tx3cb4999f-3e3a-4b4c-9131-4aa414e5edc2) Apr 4 15:00:32 blazer1 object-server STDOUT: WARNING:root:posix_fadvise(16, 0, 116, 4) -> 22 (txn: txea4c9a2c-78e6-464d-94df-2f74734e9ee2) Apr 4 15:00:48 blazer1 object-server STDOUT: WARNING:root:posix_fadvise(13, 0, 116, 4) -> 22 (txn: txd9da848b-e3c6-4023-9bfe-afd4f204f582) Apr 4 15:01:03 blazer1 object-server STDOUT: WARNING:root:posix_fadvise(16, 0, 207, 4) -> 22 (txn: txbde0e21d-443e-4d0a-ac6e-2365d8c452e0) Apr 4 15:51:49 blazer1 object-auditor STDOUT: WARNING:root:posix_fadvise(15, 0, 1114112, 4) -> 22 Apr 4 15:51:49 blazer1 object-auditor STDOUT: WARNING:root:posix_fadvise(15, 1114112, 1114112, 4) -> 22 Apr 4 15:51:49 blazer1 object-auditor STDOUT: WARNING:root:posix_fadvise(15, 2228224, 1114112, 4) -> 22 Apr 4 15:51:49 blazer1 object-auditor STDOUT: WARNING:root:posix_fadvise(15, 3342336, 1114112, 4) -> 22 Apr 4 15:51:49 blazer1 object-auditor STDOUT: WARNING:root:posix_fadvise(15, 4456448, 1114112, 4) -> 22

I managed to trace the following system call in the object-server and it seems that the posix_fadvise funtion is not called correctly (the advice value should be 4 but in this case it is the huge value 0xa00000): [pid 17125] fadvise64(7, 0, 0, 0xa00000 /* POSIX_FADV_??? */) = -1 EINVAL (Invalid argument)

This makes it hard to read the swift error logs, especially when the auditor is running. Is this a known problem?