On Tue, 22 Sep 2020 14:18:24 +0100 "Richard Purdie" <[email protected]> wrote:
> This can happen when files are deleted outside of pseudo context and > the inode is reused by a new file which pseduo then "sees". In terms of the original design: This would be considered a usage bug, and pseudo issues diagnostics for that. Once files are owned by an instance of pseudo, it expects to "see" every change to those files, and if you don't do that, then yes, the database is corrupt. But in some cases, the behavior was something like "a move within a pseudo filesystem" or something similar, and losing the data would also be bad. Basically, the original design philosophy is that you should *never* be modifying things pseudo owns outside of pseudo. And that does impose a performance cost on things, *but*, it also gives us a lot of confidence in results. So my preference on "deleting files outside of pseudo context, inode gets reused" would be "don't do that then"; this is why pseudo reports diagnostics for those. Being able to tell you what the old path was in such cases was actually one of the primary reasons pseudo exists. -s
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#142725): https://lists.openembedded.org/g/openembedded-core/message/142725 Mute This Topic: https://lists.openembedded.org/mt/77012533/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
