sjw

The file activity plugin itself is opening some directories on the system, causing my disks spin up. Any clues? Used the following script and got the log while true; do OUTPUT=$(lsof /mnt/disk*) if [ -n "$OUTPUT" ]; then echo "$(date '+%H:%M:%S') - Open files detected:" echo "$OUTPUT" echo "----------------------------------------" fi sleep 1 done COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME fileactiv 19817 root 4r DIR 9,1 4096 2672870747 /mnt/disk1/backup/subdir... ---------------------------------------- 20:55:44 - Open files detected: COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME fileactiv 19817 root 4r DIR 9,1 188416 21382526367 /mnt/disk1/backup/subdir... ---------------------------------------- 20:55:48 - Open files detected: COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME fileactiv 19817 root 4r DIR 9,1 4096 2652959028 /mnt/disk1/backup/subdir... ---------------------------------------- 20:55:50 - Open files detected: COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME fileactiv 19817 root 4r DIR 9,1 4096 5054462461 /mnt/disk1/backup/subdir... ---------------------------------------- 20:55:54 - Open files detected: COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME fileactiv 19817 root 4r DIR 9,1 4096 13355131989 /mnt/disk1/backup/subdir...

With the "Preserve user defined networks" disabled, my custom network was retained after docker restart or server restart. The help message for the setting states the followings: Did my custom network survive after Docker/Server restart because there are containers that are referencing the custom network?