Hi, Richard,

> Even if you can't reproduce the error, you can likely look at the pseudo
> database (in WORKDIR/pseudo/) as it is a relatively simple sqlite3 database. 
> You
> can check the inode numbers in the database compared to the files on disk and
> the issue is fixed when the numbers match up.

I have checked files.db but it did not help. I have found that ino in
sqllite db is what is printed in pseudo.log, and, it does not match
actual ino on the file system, as it is printed in pseudo.log too:

  inode mismatch:
'../kernel-module-smth/1.0-r0/image/lib/modules/5.10.25-yocto-standard/extra/smth.ko'
ino 701049753 in db, 639582649 in request.

The question is what has led to this mismatch. How can I debug it when
I get this situation randomly (or not randomly, but pattern is not
clear for me at the moment)?

Kind regards,
Vasyl
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#157649): 
https://lists.openembedded.org/g/openembedded-core/message/157649
Mute This Topic: https://lists.openembedded.org/mt/85906790/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to