When I try "deja-dup --backup" on the command line, I get a message that it is a "creating a fresh backup to protect against backup corruption. This will take longer than normal".
I ran the process with `strace`, saved the output to a logfile, and waited several hours for the crash to happen again. Then I went to review the 29G file that had been generated.
Ignoring the flood of polling related entries, I focused on noting the last files that were accessed before the process crashed. Here are those last related lines of the `strace` output:
So it looks like the GVFS metadata file was the last one to be accessed. I presume the `unlink` and `rmdir` calls are part of a clean-up at the end and happened after the error.
When I try "deja-dup --backup" on the command line, I get a message that it is a "creating a fresh backup to protect against backup corruption. This will take longer than normal".
I ran the process with `strace`, saved the output to a logfile, and waited several hours for the crash to happen again. Then I went to review the 29G file that had been generated.
Ignoring the flood of polling related entries, I focused on noting the last files that were accessed before the process crashed. Here are those last related lines of the `strace` output:
``` "/home/ mark/.local/ share/gvfs- metadata" , {f_type= EXT2_SUPER_ MAGIC, f_bsize=4096, f_blocks=50211842, f_bfree=9505 {val=[379187708 0, 1636325322]}, f_namelen=255, f_frsi ST_VALID| ST_RELATIME} ) = 0 mark/.local/ share/gvfs- metadata/ home", O_RDONLY) = 16 S_IFREG| 0600, st_size=337916, ...}) = 0 "/home/ mark/.local/ share/gvfs- metadata" , {f_type= EXT2_SUPER_ MAGIC, f_bsize=4096, f_blocks=50211842, f_bfree=9505 {val=[379187708 0, 1636325322]}, f_namelen=255, f_frsi ST_VALID| ST_RELATIME} ) = 0 mark/.local/ share/gvfs- metadata/ home-b5c635b8. log", O_RDONLY) = 18 S_IFREG| 0644, st_size=32768, ...}) = 0 EFD_NONBLOCK) = 20 d5490, FUTEX_WAKE_PRIVATE, 1) = 1 c0810, FUTEX_WAKE_PRIVATE, 1) = 1 cc0c8, FUTEX_WAKE_PRIVATE, 1) = 1 a0fe0, FUTEX_WAKE_PRIVATE, 2147483647) = 0 "/home/ mark/.cache/ deja-dup/ metadata" ) = -1 EISDIR (Is a directory) /home/mark/ .cache/ deja-dup/ metadata" ) = 0 /home/mark/ .cache/ deja-dup" , {st_mode= S_IFDIR| 0755, st_size=4096, ...}) = 0 /home/mark/ .cache" , {st_mode= S_IFDIR| 0700, st_size=4096, ...}) = 0 S_IFDIR| 0755, st_size=24576, ...}) = 0 S_IFDIR| 0755, st_size=4096, ...}) = 0 S_IFDIR| 0755, st_size=4096, ...}) = 0
statfs(
524, f_bavail=6949148, f_files=12763136, f_ffree=11482383, f_fsid=
ze=4096, f_flags=
openat(AT_FDCWD, "/home/
fstat(16, {st_mode=
mmap(NULL, 337916, PROT_READ, MAP_SHARED, 16, 0) = 0x7fec716eb000
statfs(
524, f_bavail=6949148, f_files=12763136, f_ffree=11482383, f_fsid=
ze=4096, f_flags=
openat(AT_FDCWD, "/home/
fstat(18, {st_mode=
mmap(NULL, 32768, PROT_READ, MAP_SHARED, 18, 0) = 0x7fec80007000
eventfd2(0, EFD_CLOEXEC|
write(6, "\1\0\0\0\0\0\0\0", 8) = 8
futex(0x55972ec
futex(0x55972ec
futex(0x55972ec
read(20, "\1\0\0\0\0\0\0\0", 16) = 8
write(20, "\1\0\0\0\0\0\0\0", 8) = 8
futex(0x55972f0
close(20) = 0
unlink(
rmdir("
lstat("
lstat("
lstat("/home/mark", {st_mode=
lstat("/home", {st_mode=
lstat("/", {st_mode=
```
So it looks like the GVFS metadata file was the last one to be accessed. I presume the `unlink` and `rmdir` calls are part of a clean-up at the end and happened after the error.
Now I need to shop for a new backup solution!