(18-04-2014 12:59)simoncn Wrote: (17-04-2014 23:49)MikeSpragg Wrote: Here you go !
Thanks very much!
This log doesn't show any activity that could cause disk I/O. Here's a summary:
23:16:06 The NAS is disconnected from the network
23:16:06 The Monitor device sends out "alive" notifications on the loopback subnet
23:24:40 The MediaServer device sends out "alive" notifications on the loopback subnet
23:29:27 The Monitor device sends out "alive" notifications on the loopback subnet
23:38:09 The MediaServer device sends out "alive" notifications on the loopback subnet
23:42:18 The Monitor device sends out "alive" notifications on the loopback subnet
23:47:42 The NAS is reconnected to the network
If MinimServer logging is set to Info, this activity will not cause anything to be written to the log and will not cause any other disk I/O from the MinimServer/Java process.
If you are seeing disk I/O with MinimServer logging set to Info, this might be caused by something else on the QNAP that is handling the network activity generated by the "alive" notifications (for example, some kind of network logging). However, the timing of this "alive" activity doesn't fit with your earlier description that the disk I/O occurs regularly every 4 to 5 minutes.
Another possibility is that ohNet is doing something every 4 to 5 minutes that isn't being logged and is causing disk I/O. From my knowledge of how ohNet works, this seems very unlikely.
Can you produce a similar complete log of disk I/O activity for a 30-minute period when the NAS is disconnected from the LAN? This would be similar to the extracts you included in this post. When doing this, please set ohnet.debug to Default and MinimServer logging to Info. If I can see the complete picture over a 30-minute period, I might be able to spot some pattern.
Hi, as I need to be connected to run the script I can't disconnect the QNAP from the LAN whilst that runs - did you still want the complete log ?
Search
Member List
Calendar
Help
