posix_fadvise syslog warnings
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Object Storage (swift) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
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:
Apr 4 15:00:32 blazer1 object-server STDOUT: WARNING:
Apr 4 15:00:48 blazer1 object-server STDOUT: WARNING:
Apr 4 15:01:03 blazer1 object-server STDOUT: WARNING:
Apr 4 15:51:49 blazer1 object-auditor STDOUT: WARNING:
Apr 4 15:51:49 blazer1 object-auditor STDOUT: WARNING:
Apr 4 15:51:49 blazer1 object-auditor STDOUT: WARNING:
Apr 4 15:51:49 blazer1 object-auditor STDOUT: WARNING:
Apr 4 15:51:49 blazer1 object-auditor STDOUT: WARNING:
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?
Related branches
- gholt (community): Approve
-
Diff: 16 lines (+2/-2)1 file modifiedswift/common/utils.py (+2/-2)
Changed in swift: | |
assignee: | nobody → FUJITA Tomonori (fujita-tomonori) |
status: | New → Fix Committed |
Changed in swift: | |
milestone: | none → 1.4.2 |
Changed in swift: | |
status: | Fix Committed → Fix Released |
This bug is based on Question #151641, but I'm seeing the behaviour too.