<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><font face="Times New Roman, Times, serif">Re: "...</font><font
face="Times New Roman, Times, serif">recursive search on a set
of folders?"</font></p>
<p><font face="Times New Roman, Times, serif">Do you mean operating
on subfolders?<br>
</font></p>
<p><font face="Times New Roman, Times, serif">I looked at the exiv2
man page (<a moz-do-not-send="true"
href="https://exiv2.org/manpage.html"
class="moz-txt-link-freetext">https://exiv2.org/manpage.html</a>),
but I found no mention of recursion into subfolders.<br>
Maybe it can generalize wildcards to include subfolders like
this: \bin\exiv2.exe -pp -q C:\photos\*\*.jpg</font></p>
<p><font face="Times New Roman, Times, serif">Bob D<br>
</font></p>
<div class="moz-cite-prefix"><font face="Times New Roman, Times,
serif">On 4/13/2023 7:02 AM, frederic chaume wrote:<br>
</font></div>
<blockquote type="cite"
cite="mid:676c0dde-8ec7-5495-5640-3c4c17a1d520@gmail.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<font face="Times New Roman, Times, serif"> Hi All<br>
</font> <font face="Times New Roman, Times, serif"><br>
I found an option using exiv2 under windows<br>
</font> <font face="Times New Roman, Times, serif"><br>
>bin\exiv2.exe -pp -q P2280067_DxO-corrupted.jpg<br>
Exiv2 exception in print action for file
P2280067_DxO-corrupted.jpg:<br>
P2280067_DxO-corrupted.jpg: The file contains data of an unknown
image type<br>
</font> <font face="Times New Roman, Times, serif"><br>
>bin\exiv2.exe -pp -q P2280067_DxO.jpg<br>
Preview 1: image/jpeg, 317x237 pixels, 17356 bytes<br>
</font> <font face="Times New Roman, Times, serif"><br>
>bin\exiv2.exe -pp -q .\P2280067.ORF<br>
Preview 1: image/jpeg, 160x120 pixels, 9080 bytes<br>
Preview 2: image/jpeg, 3200x2400 pixels, 1060974 bytes<br>
</font> <font face="Times New Roman, Times, serif"><br>
I think that could be a good solution to find corrupted jpeg.
Based on this I have some thought<br>
- as exiv2 is native with Digikam, I guess such error could be
visible? <b>Is there some "debug level" or some logs somewhere
that could report such errors ?</b><br>
- I'm not expert on coding so don't know how to translate such
command to a recursive search on a set of folders?<br>
- seems to apply to raw also , but I don't have corrupted raw to
perform the test<br>
</font> <font face="Times New Roman, Times, serif"><br>
thanks to share your feedbacks and may be other option<br>
</font> <font face="Times New Roman, Times, serif"><br>
Frederic<br>
</font> <font face="Times New Roman, Times, serif"><br>
</font> <font face="Times New Roman, Times, serif"><br>
</font> <font face="Times New Roman, Times, serif"><br>
</font> <font face="Times New Roman, Times, serif"><br>
</font>
<div class="moz-cite-prefix"><font face="Times New Roman, Times,
serif">Le 11/04/2023 à 18:13, <a
class="moz-txt-link-abbreviated moz-txt-link-freetext"
href="mailto:plowmail2010@gmail.com" moz-do-not-send="true">plowmail2010@gmail.com</a>
a écrit :<br>
</font> </div>
<blockquote type="cite"
cite="mid:dd9e209a-f400-3a26-b5b9-aebc4eab3111@gmail.com">
<meta http-equiv="Content-Type" content="text/html;
charset=UTF-8">
<p><font face="Times New Roman, Times, serif">Yes, disk space
can be a problem. On the other hand, compare the cost of
disks to the value of your files. 1 TB SSD's run about $65
USD. A 2 TB disk is about $60.<br>
</font> <font face="Times New Roman, Times, serif">My search
for "validate jpg files" revealed several candidates, but
they seem intended for programmer/geek people. For example,
the JPG data begin with FFD8 hex and end with FFD9. So all
you need do is find or write a program to test for those
values. And sure enough, people have done that, if you can
figure out how to build/install on unix/linux.<br>
Maybe this repair site will help: <a moz-do-not-send="true"
href="https://online.officerecovery.com/pixrecovery/"
class="moz-txt-link-freetext">https://online.officerecovery.com/pixrecovery/</a>
I have not tried it.<br>
(Confession: I am a former programmer/geek. Now I am just a
geek.)</font></p>
<p><font face="Times New Roman, Times, serif">Bob<br>
</font> </p>
<div class="moz-cite-prefix"><font face="Times New Roman, Times,
serif">On 4/11/2023 10:51 AM, frederic chaume wrote:<br>
</font> </div>
<blockquote type="cite"
cite="mid:5b7617a2-63c3-7570-8361-1ae7e31e6b43@gmail.com"><font
face="Times New Roman, Times, serif">I'm using FreefileSync
each time I import new raw files. It includes a version
management, but I had to remove it the because of the disk
space used, so today I'm relying on the network trashbin
plus a regular backup on an another disk. <br>
But clearly not enough 🙁 <br>
</font> <font face="Times New Roman, Times, serif"><br>
What could help is to be able to validate the integrity of
the collections and/or the backup. So if any idea is welcome
<br>
</font> <font face="Times New Roman, Times, serif"><br>
Frederic <br>
</font> <font face="Times New Roman, Times, serif"><br>
</font> <font face="Times New Roman, Times, serif"><br>
Le 11/04/2023 à 16:34, <a class="moz-txt-link-abbreviated
moz-txt-link-freetext"
href="mailto:plowmail2010@gmail.com"
moz-do-not-send="true">plowmail2010@gmail.com</a> a
écrit : <br>
</font>
<blockquote type="cite"><font face="Times New Roman, Times,
serif">On 4/11/2023 6:30 AM, frederic chaume wrote: <br>
</font>
<blockquote type="cite"><font face="Times New Roman, Times,
serif">my concern is that running another backup may
overwrite the correct file by a acorrupted version,
that's why I'm trying to make a check before another
backup <br>
</font> </blockquote>
<font face="Times New Roman, Times, serif"><br>
Off on a tangent... <br>
If your backup procedure can overwrite older backups, you
need to use a better backup. <br>
I, too, am a victim of Windows. <br>
I use Macrium Reflect ($69 USD). <br>
I don't know how to make it overwrite earlier backups.
It's probably impossible. <br>
</font> <font face="Times New Roman, Times, serif"><br>
Bob <br>
</font> <font face="Times New Roman, Times, serif"><br>
</font> </blockquote>
<font face="Times New Roman, Times, serif"><br>
</font> </blockquote>
</blockquote>
<font face="Times New Roman, Times, serif"><br>
</font> </blockquote>
</body>
</html>