Carlos Capriotti
Dabbler
- Joined
- Mar 2, 2015
- Messages
- 22
Hello all.
I've posted something similar under "performance", but now I am more convinced this might be a real bug.
Here is the scenario: Two Dell PE T610s working side by side.
"Problem-server" is a freshly installed FreeNAS 9.3 with the latest update applied, but nothing else configured, except for networking, in order to gain access to the internet (for updates).
"Control-server"is its brother with a very similar but not identical configuration, behaving well, as expected.
Problem-server shows an average load on "top", "system processes" and on the reporting graphs, which is consistent and always between 0.6 and 0.7. Top and "processes" show nothing using the CPU.
The only difference that could matter between problem and control servers is that "problem" server is generation one, and control is generation 2. This may not be meaningful, since problem server was tested with CentOS 6.5 and the symptom was not present.
Now, before getting too serious about this as an official bug report, I thought of discussing it first.
Let me know what specifics you would like to know about this system.
Thank you.
I've posted something similar under "performance", but now I am more convinced this might be a real bug.
Here is the scenario: Two Dell PE T610s working side by side.
"Problem-server" is a freshly installed FreeNAS 9.3 with the latest update applied, but nothing else configured, except for networking, in order to gain access to the internet (for updates).
"Control-server"is its brother with a very similar but not identical configuration, behaving well, as expected.
Problem-server shows an average load on "top", "system processes" and on the reporting graphs, which is consistent and always between 0.6 and 0.7. Top and "processes" show nothing using the CPU.
The only difference that could matter between problem and control servers is that "problem" server is generation one, and control is generation 2. This may not be meaningful, since problem server was tested with CentOS 6.5 and the symptom was not present.
Now, before getting too serious about this as an official bug report, I thought of discussing it first.
Let me know what specifics you would like to know about this system.
Thank you.