Post Reply 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
MinimServer & HDD Sleep
19-04-2014, 12:33
Post: #31
RE: MinimServer & HDD Sleep
(19-04-2014 12:23)simoncn Wrote:  
(19-04-2014 01:30)MikeSpragg Wrote:  Hi Simon, OK - did an & version - which is attached. Unfortunately, very much the same (with LAN disconnected).

I think the significant activity is this:

After 200 seconds idle (A):

6277.220366] setcfg(32122): dirtied inode 6894 (CACHEDEV2_DATA.log.bak) on md9
<7>[316277.222210] setcfg(32123): dirtied inode 6929 (CACHEDEV2_DATA.log.bak) on md9
<7>[316277.225515] sed(32135): dirtied inode 6894 (CACHEDEV2_DATA.logafg0VQ) on md9
<7>[316277.273074] setcfg(32245): dirtied inode 6875 (vg1.log) on md9
<7>[316277.273326] setcfg(32245): dirtied inode 6929 (vg1.log.bak) on md9
<7>[316277.275816] sed(32248): dirtied inode 6875 (vg1.logbqqQfW) on md9

After 360 seconds idle (B):

<4>[316658.692110] md1_raid1(2930): WRITE block 982422920 on sda (3 sectors)
<4>[316658.703745] md1_raid1(2930): WRITE block 982422928 on sda (1 sectors)
<4>[316658.705889] md1_raid1(2930): WRITE block 982422920 on sda (3 sectors)
<4>[316658.710775] md1_raid1(2930): WRITE block 458626512 on sda (8 sectors)
<4>[316658.911573] md1_raid1(2930): WRITE block 982422920 on sda (3 sectors)
<4>[316658.914570] md1_raid1(2930): WRITE block 982422928 on sda (1 sectors)

After 194 seconds idle (C):

<7>[316877.204889] setcfg(8202): dirtied inode 6894 (CACHEDEV2_DATA.log) on md9
<7>[316877.205145] setcfg(8202): dirtied inode 6929 (CACHEDEV2_DATA.log.bak) on md9
<7>[316877.206453] setcfg(8203): dirtied inode 6894 (CACHEDEV2_DATA.log.bak) on md9
<7>[316877.207791] setcfg(8204): dirtied inode 6929 (CACHEDEV2_DATA.log.bak) on md9
<7>[316877.210302] sed(8207): dirtied inode 6894 (CACHEDEV2_DATA.log2o16UQ) on md9
<7>[316877.251374] setcfg(8240): dirtied inode 6875 (vg1.log) on md9
........
setcfg(8240): dirtied inode 6929 (vg1.log.bak) on md9
<7>[316877.254570] sed(8248): dirtied inode 6875 (vg1.logZ1OesT) on md9
<7>[316877.348734] setcfg(8389): dirtied inode 6808 (vg2.log) on md9
<7>[316877.348998] setcfg(8389): dirtied inode 6929 (vg2.log.bak) on md9
<7>[316877.351538] sed(8392): dirtied inode 6808 (vg2.logNdGDq0) on md9

After 154 seconds idle (D):

<7>[317128.917441] log_tool(12461): dirtied inode 13282 (event.log) on md9
<7>[317128.917871] log_tool(12461): dirtied inode 13300 (event.log-journal) on md9

In (A) and (C) there are references to vg1.log and vg2.log. These seem to be associated with valgrind (a debugging tool). Is it possible that the QTS 4.1 beta firmware contains valgrind debugging code that is writing to these log files? Can you look at these log files to see what they contain?

Hi Simon, think that's a red-herring - it appears to be a log of disk usage (the QNAP records disk usage) in :

[/] # find / -name vg*.log
/mnt/HDA_ROOT/.config/storage_usage_history/vg1.log
/mnt/HDA_ROOT/.config/storage_usage_history/vg2.log
[/] # cd /mnt/HDA_ROOT/.config/storage_usage_history
[/mnt/HDA_ROOT/.config/storage_usage_history] # ls -l
-rw-r--r-- 1 admin administ 16686 Apr 19 01:40 CACHEDEV2_DATA.log
-rw-r--r-- 1 admin administ 16046 Apr 19 01:40 vg1.log
-rw-r--r-- 1 admin administ 16634 Apr 19 01:40 vg2.log

Which, if the disk is being written to - would explain why this is being logged (as it's usage).


Attached File(s)
.zip  Public.zip (Size: 4.27 KB / Downloads: 2)
Find all posts by this user
Quote this message in a reply
19-04-2014, 16:20
Post: #32
RE: MinimServer & HDD Sleep
(19-04-2014 12:33)MikeSpragg Wrote:  Hi Simon, think that's a red-herring - it appears to be a log of disk usage (the QNAP records disk usage) in :

[/] # find / -name vg*.log
/mnt/HDA_ROOT/.config/storage_usage_history/vg1.log
/mnt/HDA_ROOT/.config/storage_usage_history/vg2.log
[/] # cd /mnt/HDA_ROOT/.config/storage_usage_history
[/mnt/HDA_ROOT/.config/storage_usage_history] # ls -l
-rw-r--r-- 1 admin administ 16686 Apr 19 01:40 CACHEDEV2_DATA.log
-rw-r--r-- 1 admin administ 16046 Apr 19 01:40 vg1.log
-rw-r--r-- 1 admin administ 16634 Apr 19 01:40 vg2.log

Which, if the disk is being written to - would explain why this is being logged (as it's usage).

Surely this will prevent the disk from spinning down, as writing the disk update history to the disk will spin up the disk, and this disk I/O to the logs will trigger writing a further history update after 10 minutes, etc., etc.

I just rechecked the log1.log and log2.log files that you produced yesterday to see if the same thing was happening. The log2.log file (wthout MinimServer running) was truncated by Ctrl-C at the 9/100 stage, but the log1.log file was allowed to terminate normally after completing the final 99/100 test. This could explain why log2.log is much smaller than log1.log.
Find all posts by this user
Quote this message in a reply
19-04-2014, 16:27 (This post was last modified: 19-04-2014 16:36 by MikeSpragg.)
Post: #33
RE: MinimServer & HDD Sleep
(19-04-2014 16:20)simoncn Wrote:  
(19-04-2014 12:33)MikeSpragg Wrote:  Hi Simon, think that's a red-herring - it appears to be a log of disk usage (the QNAP records disk usage) in :

[/] # find / -name vg*.log
/mnt/HDA_ROOT/.config/storage_usage_history/vg1.log
/mnt/HDA_ROOT/.config/storage_usage_history/vg2.log
[/] # cd /mnt/HDA_ROOT/.config/storage_usage_history
[/mnt/HDA_ROOT/.config/storage_usage_history] # ls -l
-rw-r--r-- 1 admin administ 16686 Apr 19 01:40 CACHEDEV2_DATA.log
-rw-r--r-- 1 admin administ 16046 Apr 19 01:40 vg1.log
-rw-r--r-- 1 admin administ 16634 Apr 19 01:40 vg2.log

Which, if the disk is being written to - would explain why this is being logged (as it's usage).

Surely this will prevent the disk from spinning down, as writing the disk update history to the disk will spin up the disk, and this disk I/O to the logs will trigger writing a further history update after 10 minutes, etc., etc.

I just rechecked the log1.log and log2.log files that you produced yesterday to see if the same thing was happening. The log2.log file (wthout MinimServer running) was truncated by Ctrl-C at the 9/100 stage, but the log1.log file was allowed to terminate normally after completing the final 99/100 test. This could explain why log2.log is much smaller than log1.log.

Not quite. It only writes the usage log after something has made it write to the disk (no write, no log).

It's just something (whilst Minim/JRE) is running that is doing this (that's why I say it's a red herring) write to disk (and then the usage is also updated).

Also, I stopped it at 9/100 as, because, it had already gotten to the half hour mark (with log2) - I waited 30 mins and there was nothing else happening. The ctrl+c was at the 30 minute marker (20:53), not 20:30 as it would appear from the log. The monitor program only writes to the log if there is activity.

With log1 it exceeded the 100 test within 30 mins. In other words - both logs are for the same period (30 mins) and log1 exceeds the test capacity of 100 tests within that period - and log2 only gets to 9/100.

In reality, these aren't "tests" at all - they are reports of disk interaction reported from the OS and then picked up by the monitor. So, they only pickup the activations as they occur.

As per readme.txt>>

Log2.log
--------

Now, with JRE/MinimServer both switched off. As you can see - a much quieter log, only 9 disk activations (at start) for the same period
and, also, disks spun down twice during the test. On the last spin down at 20:35 they stayed spun down.


20:28 - disks shutdown - Status LED Off - at 20:30 they restart (reasons unknown, spurious as.... next)
20:35 - disks shutdown - Status LED Off - and stay shutdown until end of test period (20:52) ....

-----------
Find all posts by this user
Quote this message in a reply
19-04-2014, 16:39
Post: #34
RE: MinimServer & HDD Sleep
(19-04-2014 16:27)MikeSpragg Wrote:  Not quite. It only writes the usage log after something has made it write to the disk (no write, no log).

My point was that writing the log is itself disk activity which would presumably trigger a further log write in 10 minutes time, unless the log writes are somehow excluded from the disk activity that is being monitored.

Quote:It's just something (whilst Minim/JRE) is running that is doing this (that's why I say it's a red herring) write to disk (and then the usage is also updated).

This is a reasonable interpretation. We still need to identify the mysterious "something". Sad

Quote:Also, I stopped it at 9/100 as, because, it had already gotten to the half hour mark (with log2) at 21:53. At 21:23 it finished logging (at 21:28 it shut the disks down) - I waited 30 mins and there was nothing else happening. The ctrl+c was at the 30 minute marker, not 21:23 as it would appear from the log. The monitor program only writes to the log if there is activity.

With log1 it exceeded the 100 test within 30 mins.

Thanks for clarifying this.

I am running a test now to see if I can get my QNAP to spin down while MinimServer is running.
Find all posts by this user
Quote this message in a reply
19-04-2014, 17:05
Post: #35
RE: MinimServer & HDD Sleep
(19-04-2014 16:39)simoncn Wrote:  I am running a test now to see if I can get my QNAP to spin down while MinimServer is running.

My NAS has spun down OK. The problem you are seeing must be either a difference in your configuration settings or something in the QNAP 4.1 beta firmware. I am running the 3.7.3 firmware.

I have the following network services and applications enabled:

Microsoft Networking (Standalone Server, all advanced options unchecked)
SSH with SFTP
Network Service Discovery, Bonjour with Web Administration
Web File Manager
DLNA Media Server
JRE
MinimServer
Optware
QDK

I have the following network services and applications disabled:

AFP
NFS
FTP
Telnet
SNMP
Web Server
Network Service Discovery, UPnP Discovery Service
Multimedia Station
Photo Station
Music Station
Download Station
Surveillance Station
iTunes Server
MySQL Server
Syslog Server
RADIUS Server
Backup Server
Antivirus
TFTP Server
VPN Service
LDAP Server
everything under Backup
everything under External Device
everything under MyCloudNAS Service
Find all posts by this user
Quote this message in a reply
19-04-2014, 18:32
Post: #36
RE: MinimServer & HDD Sleep
(19-04-2014 17:05)simoncn Wrote:  
(19-04-2014 16:39)simoncn Wrote:  I am running a test now to see if I can get my QNAP to spin down while MinimServer is running.

My NAS has spun down OK. The problem you are seeing must be either a difference in your configuration settings or something in the QNAP 4.1 beta firmware. I am running the 3.7.3 firmware.

I have the following network services and applications enabled:

Microsoft Networking (Standalone Server, all advanced options unchecked)
SSH with SFTP
Network Service Discovery, Bonjour with Web Administration
Web File Manager
DLNA Media Server
JRE
MinimServer
Optware
QDK

I have the following network services and applications disabled:

AFP
NFS
FTP
Telnet
SNMP
Web Server
Network Service Discovery, UPnP Discovery Service
Multimedia Station
Photo Station
Music Station
Download Station
Surveillance Station
iTunes Server
MySQL Server
Syslog Server
RADIUS Server
Backup Server
Antivirus
TFTP Server
VPN Service
LDAP Server
everything under Backup
everything under External Device
everything under MyCloudNAS Service

OK, well hopefully you'll go to 4.1 soon (it's the future!) so we can see again then. Thanks very much for taking the time anyway, cheers, Mike
Find all posts by this user
Quote this message in a reply
19-04-2014, 19:20
Post: #37
RE: MinimServer & HDD Sleep
(19-04-2014 18:32)MikeSpragg Wrote:  OK, well hopefully you'll go to 4.1 soon (it's the future!) so we can see again then. Thanks very much for taking the time anyway, cheers, Mike

It doesn't sound like a very good future, given the problems you are having. Sad

Have you checked your settings to see whether they are different from mine? In particular, I suggest you look at these:

Quote:I have the following network services and applications enabled:

Microsoft Networking (Standalone Server, all advanced options unchecked)

I have the following network services and applications disabled:

Network Service Discovery, UPnP Discovery Service

If your settings for these two items are different, this could explain the problem.
Find all posts by this user
Quote this message in a reply
19-04-2014, 20:10
Post: #38
RE: MinimServer & HDD Sleep
(19-04-2014 19:20)simoncn Wrote:  
(19-04-2014 18:32)MikeSpragg Wrote:  OK, well hopefully you'll go to 4.1 soon (it's the future!) so we can see again then. Thanks very much for taking the time anyway, cheers, Mike

It doesn't sound like a very good future, given the problems you are having. Sad

Have you checked your settings to see whether they are different from mine? In particular, I suggest you look at these:

Quote:I have the following network services and applications enabled:

Microsoft Networking (Standalone Server, all advanced options unchecked)

I have the following network services and applications disabled:

Network Service Discovery, UPnP Discovery Service

If your settings for these two items are different, this could explain the problem.

Unfortunately, it's software - the upgrade is inevitable :-)

Microsoft Networking (Standalone Server)
Advanced -
Local Browser (Checked)
Allow only NTLMv2 [you won't have this]
Enable Async I/O (Highest SMB v2.0) [you won't have this]
Are all checked

Network Service Discovery,
UPnP Discovery Service (Checked) - will uncheck
Bonjour (Checked) - although this isn't needed so will uncheck it.
Find all posts by this user
Quote this message in a reply
19-04-2014, 21:08
Post: #39
RE: MinimServer & HDD Sleep
(19-04-2014 20:10)MikeSpragg Wrote:  Unfortunately, it's software - the upgrade is inevitable :-)

It isn't inevitable unless the current version breaks for some reason. No sign of that at the moment.

Quote:Microsoft Networking (Standalone Server)
Advanced -
Local Browser (Checked)

I have found it is essential to disable Local Master Browser to get spin-down to work.

Quote:Allow only NTLMv2 [you won't have this]

I do have this checkbox. It is unchecked but I don't this would make a difference.

Quote:Enable Async I/O (Highest SMB v2.0) [you won't have this]
Are all checked

Network Service Discovery,
UPnP Discovery Service (Checked) - will uncheck
Bonjour (Checked) - although this isn't needed so will uncheck it.
Find all posts by this user
Quote this message in a reply
19-04-2014, 21:12
Post: #40
RE: MinimServer & HDD Sleep
(19-04-2014 21:08)simoncn Wrote:  
(19-04-2014 20:10)MikeSpragg Wrote:  Unfortunately, it's software - the upgrade is inevitable :-)

It isn't inevitable unless the current version breaks for some reason. No sign of that at the moment.

Quote:Microsoft Networking (Standalone Server)
Advanced -
Local Browser (Checked)

I have found it is essential to disable Local Master Browser to get spin-down to work.

Quote:Allow only NTLMv2 [you won't have this]

I do have this checkbox. It is unchecked but I don't this would make a difference.

Quote:Enable Async I/O (Highest SMB v2.0) [you won't have this]
Are all checked

Network Service Discovery,
UPnP Discovery Service (Checked) - will uncheck
Bonjour (Checked) - although this isn't needed so will uncheck it.

That's odd - never disabled master browser and, of course, spin down does occur. Just checked system since other changes, still running (led on) so I can make this change but fear it won't make a difference.
Find all posts by this user
Quote this message in a reply
Post Reply 


Forum Jump:


User(s) browsing this thread: 1 Guest(s)