Comment 10 for bug 2043716

Revision history for this message
smelis (stefanmelis) wrote :

Some more info that might help solve it. I'm seeing this too on Ubuntu 22.04.4 LTS
Duplicity slowly started eating away at memory recently, until it consumes all and OOM's.

ps aux:

USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
user 274550 99.7 69.7 140278804 137900288 ? Rsl 10:53 41:10 /usr/bin/python3.10 /usr/bin/duplicity collection-status --include=/home/user/.cache/deja-dup/metadata --exclude=/home/user/snap/*/*/.cache --exclude=/home/user/.var/app/*/cache --include=/data/dig/docker_volume --exclude=/home/user/.local/share/Trash --exclude=/home/user/.cache/deja-dup --exclude=/home/user/.cache --include=/home/user --exclude=/sys --exclude=/run --exclude=/proc --exclude=/dev --exclude=/var/tmp --exclude=/tmp --exclude=/media/user/backup/gargantua --exclude=** --exclude-if-present=CACHEDIR.TAG --exclude-if-present=.deja-dup-ignore gio+file:///media/user/backup/gargantua --no-encryption --verbosity=9 --timeout=120 --archive-dir=/home/user/.cache/deja-dup --tempdir=/tmp --log-fd=16

After 20 minutes more, all RAM is consumed:

USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
user 274550 99.3 96.8 194902916 191371264 ? Rsl 10:53 63:42 /usr/bin/python3.10 /usr/bin/duplicity collection-status ...

free:
               total used free shared buff/cache available
Mem: 188Gi 185Gi 1,2Gi 751Mi 1,3Gi 345Mi
Swap: 0B 0B 0B

/var/log/kern.log OOM, monitor kills process:

Jun 4 11:59:41 gargantua kernel: [245789.662663] oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=user.slice,mems_allowed=0,global_oom,task_memcg=/user.slice/user-1000.slice/user@1000.service/app.slice/app-gnome-org.gnome.DejaDup.Monitor-6739.scope,task=duplicity,pid=274550,uid=1000
Jun 4 11:59:41 gargantua kernel: [245789.662676] Out of memory: Killed process 274550 (duplicity) total-vm:196347780kB, anon-rss:192909824kB, file-rss:1792kB, shmem-rss:0kB, UID:1000 pgtables:382104kB oom_score_adj:0

What might be a hint as to what's going on are the repeated:

Jun 4 12:22:53 gargantua kernel: [247182.016664] ntfs3: 121981 callbacks suppressed
Jun 4 12:22:53 gargantua kernel: [247182.016667] ntfs3: sda1: ino=774bf, "gargantua" Looks like your dir is corrupt

that fill up /var/log/kern.log

The media the backup is written to is an external Seagate with NTFS fs (which seems to have a corrupt "gargantua" directory, which is where the backup should go).