Threaded Mode | Linear Mode

MikeSpragg · 19-04-2014, 12:33

(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).