https://bugs.kde.org/show_bug.cgi?id=476688

            Bug ID: 476688
           Summary: Importing pictures on NTFS partition results in FS
                    corruption and data loss
    Classification: Applications
           Product: digikam
           Version: 8.1.0
          Platform: Fedora RPMs
                OS: Linux
            Status: REPORTED
          Severity: critical
          Priority: NOR
         Component: general
          Assignee: digikam-bugs-n...@kde.org
          Reporter: kitt...@gmail.com
  Target Milestone: ---

Created attachment 162934
  --> https://bugs.kde.org/attachment.cgi?id=162934&action=edit
Chkdsk sample log

SUMMARY
Importing pictures to with Digikam to a NTFS partition, results in corruption
of the $I30 index in the destination folder, leading to a silent corruption and
data loss. 


STEPS TO REPRODUCE
1. Import pictures to a NTFS partition
2. Check the partition with Windows chkdsk
3. 

OBSERVED RESULT
Chkdsk reports the FS as damaged, requiring a repair run. Some files are either
missing or inaccessible prior to repair, both from Linux and Windows, some
other are irremediably lost if overwritten.

EXPECTED RESULT
No corruption nor data loss.

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 38
KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.110.0
Qt Version: 5.15.11
Kernel Version: 6.5.9-200.fc38.x86_64 (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz
Memory: 15.5 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Manufacturer: Dell Inc.
Product Name: Inspiron 5570

ADDITIONAL INFORMATION
I am attaching a demo log of a chkdsk run, after I intentionally imported
photos with digikam to trigger the corruption. I also briefly tried to match
files marked by chkdsk as repaired/damaged against my Fedora journal, finding
nothing. 
Unfortunately, I did not have time to understand Digikam's code well enough to
perform deeper analysis in a wise way. 

The real problem is, I have noticed this behavior by chance because my backup
system started hanging and throwing nonsense errors. I then found out it hung
on parts of the NTFS that were corrupted and hence traced the issue back to
Digikam. All this means the problem started who knows how many months ago, and
I have no more clean copies of my data left to restore from. Same for my family
members and some friends, and we all have definitively lost different amounts
of data.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to