Am Sonntag, 28. Januar 2018, 13:13:20 CET schrieb Matthias Bodenbinder:
> I did an strace and found that DT is trying to stat a DCIM folder in the
> cloud:
>
> 4969 stat("/mnt/magentacloud/DCIM", <unfinished ...>
> 4969 stat("/mnt/magentacloud/dcim", 0x7ff6b7ff0330) = -1 ENOENT (No such
> file or directory)
>
> Why is that? What has DT to do with this directory?
As "DCIM" is part of the file layout of cameras I would guess that it's
gphoto2. Let's find out.
Please start darktable in gdb, make it hang and then get a backtrace:
gdb darktable
r
<make it hang>
ctrl-c
set pagination off
set logging file gdb.txt
set logging on
thread apply all bt full
c
<wait for dt to recover and close dt>
q
Then show us the generated file "gdb.txt".
> As long as dd is writing to /mnt/magentacloud the drive is not responding.
> Even simple "ls" commands are waitng until the dd command is finished. So
> the "stat" from DT must wait also.
>
> DT is actually doing a "stat" on every mounted directory in /mnt:
That sounds like gphoto2 looking for removable media.
> 4969 stat("/mnt/magentacloud/DCIM", <unfinished ...>
> 4969 stat("/mnt/magentacloud/dcim", 0x7ff6b7ff0330) = -1 ENOENT (No such
> file or directory) 4969 stat("/mnt/zstore/DCIM", 0x7ff6b7ff0330) = -1
> ENOENT (No such file or directory) 4969 stat("/mnt/zstore/dcim",
> 0x7ff6b7ff0330) = -1 ENOENT (No such file or directory) 4969
> stat("/mnt/zstore/BENCHMARK/DCIM", 0x7ff6b7ff0330) = -1 ENOENT (No such
> file or directory) 4969 stat("/mnt/zstore/BENCHMARK/dcim", 0x7ff6b7ff0330)
> = -1 ENOENT (No such file or directory)
>
> Why is it doing that?
>
>
> Kind Regards
> Matthias
>
> Matthias
Tobias
[...]
signature.asc
Description: This is a digitally signed message part.
