[SOLVED]qBittorrent.conf continuously written since V3.1.4

[bob23450]

Hi
I'm new to the forum and I whish to say hello to everyone!

I use qbittorrent-nox on a Raspberry Pi (ARM linux board) with Raspbian (Debian derivative) and since version 3.1.4 I noticed a continuous write access to the root filesystem (that is on an SD card) even when no torrents are being up/down-loaded.
It turned out that the qBittorrent configuration file (~/.config/qBittorrent/qBittorrent.conf) is always updated (maybe other files are, but I could not detect them).
The program works well anyways, still I'm concerned about an excessive wearout of the SD card (notice that I usually direct the downloads to an external USB disk which isn't affected by this problem).
I'm just curious about this change (v3.1.3 behaves differently) and whether I can reduce such write activity.

Regards
bz

[loki]

Wear on SD cards is only when writing or rewriting data, you can have it access (read) files constantly without damage.
Write access and active writing is 2 different things, you do have to allow write access to save settings and progress.

[bob23450]

Hi loki!
Indeed there are data that need to be saved in order to make the program work correctly. What I noticed is an increase of the frequency at which those data are saved, since 3.1.4.
I found out that stats about the amount of data uploaded and downloaded are written every second to qBittorrent.conf. I can't tell with which frequency they actually get written to the flash card, but the activity (either read OR write) LED flashes roughly once a second.
Maybe I should not worry much about this, nevertheless I think that slowing down a bit the frequency of such writes - once a minute or so - would not impair too much the program's functionality (I guess the periodic save is meant to ensure updated stats in case of crash or when the system is not properly shut down).

[cshadow]

I can confirm the issue with v3.1.4. Qbittorrent is writing to disk even with no torrents running.
Can someone confirm if the problem still exists in v3.1.5?
I just set the file to read-only and the writing stopped
Why it has to write the config file so often, shouldn't it be written ONLY when user makes some changes?

iotop shows this proces writing at some 11K/s

Code: Select all

11.36 K/s  0.00 %  0.00 % qbittorrent [TorrentSpeedMon]

Frequency of the writes is quite high:

Code: Select all

Jan 25 22:02:50 witch64 kernel: [570047.623369] TorrentSpeedMon(3116): WRITE block 28401808 on sda1 (24 sectors)
Jan 25 22:02:51 witch64 kernel: [570048.627449] TorrentSpeedMon(3116): WRITE block 54254736 on sda1 (24 sectors)
Jan 25 22:02:52 witch64 kernel: [570049.631724] TorrentSpeedMon(3116): WRITE block 28401832 on sda1 (24 sectors)
Jan 25 22:02:53 witch64 kernel: [570050.639601] TorrentSpeedMon(3116): WRITE block 54254760 on sda1 (24 sectors)
Jan 25 22:02:54 witch64 kernel: [570051.647656] TorrentSpeedMon(3116): WRITE block 28401856 on sda1 (24 sectors)
Jan 25 22:02:55 witch64 kernel: [570052.652308] TorrentSpeedMon(3116): WRITE block 54256352 on sda1 (24 sectors)
Jan 25 22:02:56 witch64 kernel: [570053.664244] TorrentSpeedMon(3116): WRITE block 54256376 on sda1 (24 sectors)
Jan 25 22:02:57 witch64 kernel: [570054.672413] TorrentSpeedMon(3116): WRITE block 28401880 on sda1 (24 sectors)
Jan 25 22:02:58 witch64 kernel: [570055.676312] TorrentSpeedMon(3116): WRITE block 54254784 on sda1 (24 sectors)
Jan 25 22:02:59 witch64 kernel: [570056.684134] TorrentSpeedMon(3116): WRITE block 54254808 on sda1 (24 sectors)
Jan 25 22:03:00 witch64 kernel: [570057.688014] TorrentSpeedMon(3116): WRITE block 28401904 on sda1 (24 sectors)
Jan 25 22:03:01 witch64 kernel: [570058.695761] TorrentSpeedMon(3116): WRITE block 28401928 on sda1 (24 sectors)
Jan 25 22:03:02 witch64 kernel: [570059.704059] TorrentSpeedMon(3116): WRITE block 28401952 on sda1 (24 sectors)
Jan 25 22:03:03 witch64 kernel: [570060.709167] TorrentSpeedMon(3116): WRITE block 28401976 on sda1 (24 sectors)
Jan 25 22:03:04 witch64 kernel: [570061.717076] TorrentSpeedMon(3116): WRITE block 28402000 on sda1 (24 sectors)
Jan 25 22:03:05 witch64 kernel: [570062.720459] TorrentSpeedMon(3116): WRITE block 28402024 on sda1 (24 sectors)
Jan 25 22:03:06 witch64 kernel: [570063.723736] TorrentSpeedMon(3116): WRITE block 28402048 on sda1 (24 sectors)
Jan 25 22:03:07 witch64 kernel: [570064.731663] TorrentSpeedMon(3116): WRITE block 22369168 on sda1 (24 sectors)
Jan 25 22:03:08 witch64 kernel: [570065.739791] TorrentSpeedMon(3116): WRITE block 28402072 on sda1 (24 sectors)
Jan 25 22:03:09 witch64 kernel: [570066.747756] TorrentSpeedMon(3116): WRITE block 54254840 on sda1 (24 sectors)
Jan 25 22:03:10 witch64 kernel: [570067.755700] TorrentSpeedMon(3116): WRITE block 54254864 on sda1 (24 sectors)
Jan 25 22:03:11 witch64 kernel: [570068.766670] TorrentSpeedMon(3116): WRITE block 54256400 on sda1 (24 sectors)
Jan 25 22:03:12 witch64 kernel: [570069.774325] TorrentSpeedMon(3116): WRITE block 28402096 on sda1 (24 sectors)
Jan 25 22:03:13 witch64 kernel: [570070.782357] TorrentSpeedMon(3116): WRITE block 54254984 on sda1 (24 sectors)
Jan 25 22:03:14 witch64 kernel: [570071.787255] TorrentSpeedMon(3116): WRITE block 22369192 on sda1 (24 sectors)
Jan 25 22:03:15 witch64 kernel: [570072.794987] TorrentSpeedMon(3116): WRITE block 22369216 on sda1 (24 sectors)
Jan 25 22:03:16 witch64 kernel: [570073.801288] TorrentSpeedMon(3116): dirtied inode 1575096 (qBittorrent.conf) on sda1
Jan 25 22:03:16 witch64 kernel: [570073.801315] TorrentSpeedMon(3116): dirtied inode 1575096 (qBittorrent.conf) on sda1

Larger log here:
http://paste.ubuntu.com/6816664/

EDIT - just found this
https://github.com/qbittorrent/qBittorrent/issues/1288