https://bugs.kde.org/show_bug.cgi?id=449102
--- Comment #2 from i...@free.fr ---
(In reply to tagwerk19 from comment #1)
> (In reply to iten from comment #0)
> > ... " id seems to have changed. Perhaps baloo was not running, and this
> > file was
> > deleted + re-created" ...
> >
> > ... The files created with rsync have modified time attributes
> > that are prior to creation time. An example:
> >
> > # LANG=C stat 801\ 001.jpg
> > File: 801 001.jpg
> > Size: 1923181 Blocks: 3760 IO Block: 4096 regular file
> > Device: 10305h/66309d Inode: 110231652 Links: 1
> > ...
> The Device and Inode are things to watch. If baloo says 'id seems to have
> changed", it's likely to be meaning these.
>
> See if these change with a run of rsync (would it really do that?).
>
> You can use balooshow to see what "metadata" baloo had indexed for the file
> and compare
> balooshow -x 801\ 001.jpg
This is baloo -x output:
=============
LANG=C balooshow -x 801\ 001.jpg
692006400010305 66309 110231652 801 001.jpg [/home/mathieu/xxxxx/801 001.jpg]
Mtime: 1313102038 2011-08-12T00:33:58
Ctime: 1641517470 2022-01-07T02:04:30
Cached properties:
Width: 2493
Height: 3280
Internal Info
Terms: Mimage Mjpeg T4 X26-2493 X27-3280
File Name Terms: F001 F801 Fjpg
XAttr Terms:
width: 2493
height: 3280
=============
Inode, device, mtime and ctime looks correct.
I will do a baloo -x and a stat on that file the next time baloo will reindex
it (that will take some time since /home is 1.5TB). Please note that I don't
run rsync between two baloo reindex, so the file should not be modified.
--
You are receiving this mail because:
You are watching all bug changes.
