Danke RedDiabolo,
das deckt sich mit einer ähnlichen Diskussion im internationalen Forum.
Bin inzwischen mal der unbekannten Disk Activity nachgegangen.
Habe fast alles incl. Hybrid Station und bis auf Samba und ftp gestoppt.
Es blieb aber trotzdem noch eine Schreibrate von ca. 5/s komischerweise auf HD uns SSD übrig, ziemlich synchron. Tatsächlich war das dann eine Kamera, die mit ftp bei Motion alarm auf die HD geschrieben hat, was aber die SSD Zugriffe nicht erklärt.
Habe dann Connection logging und Motion alarm abgestellt, trotzdem noch in 130s 86 Writes mit
blkdevMonitor_20151225.sh
============= 14/100 test, Mon Jun 4 13:41:12 CEST 2018 ===============
<7>[ 3504.828386] smbd(8782): dirtied inode 54657032 (gencache_notrans.tdb) on dm-8
<7>[ 3504.828401] smbd(8782): dirtied inode 54657032 (gencache_notrans.tdb) on dm-8
<7>[ 3504.832873] cleanupd(12416): dirtied inode 54657040 (serverid.tdb) on dm-8
<7>[ 3504.832885] cleanupd(12416): dirtied inode 54657040 (serverid.tdb) on dm-8
<7>[ 3504.835735] smbd(11001): dirtied inode 54657056 (smbXsrv_client_global.tdb) on dm-8
<7>[ 3504.835751] smbd(11001): dirtied inode 54657056 (smbXsrv_client_global.tdb) on dm-8
<7>[ 3564.891536] smbd(11001): dirtied inode 54657032 (gencache_notrans.tdb) on dm-8
<7>[ 3564.891549] smbd(11001): dirtied inode 54657032 (gencache_notrans.tdb) on dm-8
<7>[ 3564.896098] cleanupd(12416): dirtied inode 54657040 (serverid.tdb) on dm-8
<7>[ 3564.896109] cleanupd(12416): dirtied inode 54657040 (serverid.tdb) on dm-8
<7>[ 3564.898841] smbd(11149): dirtied inode 54657056 (smbXsrv_client_global.tdb) on dm-8
<7>[ 3564.898857] smbd(11149): dirtied inode 54657056 (smbXsrv_client_global.tdb) on dm-8
<7>[ 3509.828197] kworker/u8:0(2735): WRITE block 4154159168 on dm-8 (16 sectors)
<7>[ 3509.828240] jbd2/dm-8-8(3235): WRITE block 3062137160 on dm-8 (8 sectors)
<7>[ 3509.846698] jbd2/dm-8-8(3235): WRITE block 3062137168 on dm-8 (8 sectors)
<7>[ 3509.846724] jbd2/dm-8-8(3235): WRITE block 3062137176 on dm-8 (8 sectors)
<7>[ 3509.846741] jbd2/dm-8-8(3235): WRITE block 3062137184 on dm-8 (8 sectors)
<7>[ 3509.846750] kworker/u8:0(2735): WRITE block 4007587848 on dm-8 (16 sectors)
<7>[ 3509.846757] jbd2/dm-8-8(3235): WRITE block 3062137192 on dm-8 (8 sectors)
<7>[ 3509.846779] jbd2/dm-8-8(3235): WRITE block 3062137200 on dm-8 (8 sectors)
<7>[ 3509.847124] kworker/u8:0(2735): WRITE block 4051960128 on dm-8 (8 sectors)
<7>[ 3509.847187] jbd2/dm-8-8(3235): WRITE block 3062137208 on dm-8 (8 sectors)
<7>[ 3514.873953] kworker/u8:0(2735): WRITE block 1984 on dm-8 (8 sectors)
<7>[ 3515.025067] kworker/u8:0(2735): WRITE block 1749025024 on dm-8 (8 sectors)
<7>[ 3515.025125] kworker/u8:0(2735): WRITE block 4152361008 on dm-8 (8 sectors)
<7>[ 3515.025157] kworker/u8:0(2735): WRITE block 0 on dm-8 (8 sectors)
<7>[ 3515.834938] jbd2/dm-8-8(3235): WRITE block 3062137216 on dm-8 (8 sectors)
..5x
<7>[ 3520.878728] kworker/u8:0(2735): WRITE block 1936 on dm-8 (8 sectors)
..3x
<7>[ 3569.890989] jbd2/dm-8-8(3235): WRITE block 3062137256 on dm-8 (8 sectors)
<7>[ 3569.910382] jbd2/dm-8-8(3235): WRITE block 3062137264 on dm-8 (8 sectors)
<7>[ 3569.910450] jbd2/dm-8-8(3235): WRITE block 3062137272 on dm-8 (8 sectors)
<7>[ 3569.910467] kworker/u8:3(1506): WRITE block 4007587848 on dm-8 (16 sectors)
<7>[ 3569.910473] jbd2/dm-8-8(3235): WRITE block 3062137280 on dm-8 (8 sectors)
<7>[ 3569.910501] jbd2/dm-8-8(3235): WRITE block 3062137288 on dm-8 (8 sectors)
<7>[ 3569.910521] jbd2/dm-8-8(3235): WRITE block 3062137296 on dm-8 (8 sectors)
<7>[ 3569.910851] kworker/u8:3(1506): WRITE block 4051960136 on dm-8 (8 sectors)
<7>[ 3569.910856] jbd2/dm-8-8(3235): WRITE block 3062137304 on dm-8 (8 sectors)
<7>[ 3574.937706] kworker/u8:3(1506): WRITE block 0 on dm-8 (8 sectors)
<7>[ 3575.179028] kworker/u8:3(1506): WRITE block 1749025024 on dm-8 (8 sectors)
<7>[ 3575.832682] jbd2/dm-8-8(3235): WRITE block 3062137312 on dm-8 (8 sectors)
4x
<7>[ 3580.871477] kworker/u8:0(2735): WRITE block 1749025032 on dm-8 (8 sectors)
<7>[ 3580.897122] kworker/u8:0(2735): WRITE block 4051697672 on dm-8 (8 sectors)
<7>[ 3580.897191] kworker/u8:0(2735): WRITE block 1936 on dm-8 (8 sectors)
<7>[ 3509.828279] md1_raid1(2359): WRITE block 15608143504 on sda3 (1 sectors)
ca. 30x
============= 15/100 test, Mon Jun 4 13:43:22 CEST 2018 ===============
Alles anzeigen
Keine Ahnung was dsa File System so beschäftigt.
Habe mal die Prozesse identifiziert:
<7>[667032.003134] smbd(5313): dirtied inode 54657032 (gencache_notrans.tdb) on dm-8
SAMBA
<7>[667032.007840] cleanupd(12227): dirtied inode 54657040 (serverid.tdb) on dm-8
<7>[667033.096317] proftpd(18607): dirtied inode 55076559 (camera) on dm-8
FTP-Server
<7>[667033.055761] kworker/u8:3(3763): WRITE block 6029766120 on dm-8 (440 sectors)
"kworker" is a placeholder process for kernel worker threads, which perform most of the actual processing for the kernel, especially in cases where there are interrupts, timers, I/O, etc. These typically correspond to the vast majority of any allocated "system" time to running processes. It is not something that can be safely removed from the system in any way,
<7>[667033.055803] jbd2/dm-8-8(2748): WRITE block 3062283504 on dm-8 (8 sectors)
The JBD is the journaling block device that sits between the file system and the block device driver. The jbd2 version is for ext4
If you are seeing a lot of activity when nothing much is running, check if any of the logs are getting a lot of updates.
As a first pass, just have a look if there are any abnormally large logs. Something like the following will show you which logs are the biggest:
ls -lS /var/log/*log | head
-rw-r--r--. 1 root root 1689690 Jun 4 12:32 /var/log/Xorg.0.log
-rw-r--r--. 1 root root 506767 Aug 18 2017 /var/log/wcstatus.log
-rw-r--r--. 1 root root 292584 May 29 10:01 /var/log/lastlog
-rw-------. 1 root root 26633 May 29 00:30 /var/log/yum.log
-rw-r--r--. 1 root root 24133 Aug 18 2017 /var/log/Xorg.9.log
-rw-r--r--. 1 root root 12413 Feb 16 10:32 /var/log/tsm-home-backup.log
-rw-r--r--. 1 root root 5555 Nov 18 2017 /var/log/Xorg.1.log
-rw-r--r--. 1 root root 3424 Jan 23 13:08 /var/log/faillog
-rw-r--r--. 1 root root 2165 Apr 30 09:15 /var/log/hostondemand-rpm.log
-rw-r--r--. 1 root root 905 Apr 3 18:35 /var/log/ecpinstall.log
<7>[666203.726074] kjournald(2096): WRITE block 554344 on md9 (8 sectors)
https://unix.stackexchange.com/questions/60618/how-to-reduce-kjournald-activity
<7>[666203.754422] qLogEngined(21980): WRITE block 360448 on md9 (8 sectors)
qLogEngined - Syslog
<7>[666210.578266] md9_raid1(2083): WRITE block 1060216 on sda1 (1 sectors)
<7>[666210.811085] md9_raid1(2083): WRITE block 1060232 on sdc1 (1 sectors)
<7>[666203.008488] md1_raid1(2287): WRITE block 15608143504 on sda3 (1 sectors)
Alles anzeigen
Siehe auch:
https://www.qnap.com/en/how-to…not-entering-standby-mode
https://wiki.qnap.com/wiki/Fin…hard_drives_from_spindown
https://forum.qnap.com/viewtopic.php?t=131537
https://www.computerbase.de/fo…tplattenzugriffe.1649301/
https://forum.qnap.com/viewtopic.php?f=55&t=118677
[FAQ]Welche Prozesse laufen auf meinem NAS
Die SSD läuft prima, SMART aklles good, latency 3ms, 2 Kameras (HD und 720p) machen gerade mal 3-5 writes/s