On Mon, 28 Sep 2020 14:38:01 +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". I'm just going to say again: The **ENTIRE REASON** pseudo exists to replace fakeroot is that fakeroot did this, and it consistently, repeatedly, reliably, resulted in horrible database corruption. If files that pseudo knows about are being deleted outside the pseudo context, that is violating a crucial precondition, and **you cannot then trust the database to make sense**. Yes, you can throw away some of the specific files when you detect them -- pseudo already did this for specific cases, like directory vs plain file mismatches -- but you should always view it as a serious bug in the rest of the environment. If it's **really** necessary to allow things to corrupt the filesystem, we need a way to tell pseudo of **specific** files that it should be forgetting about or disregarding. But, in general, "a thing that isn't under pseudo is modifying the part of the filesystem pseudo thinks it owns" means "your entire database is presumptively corrupt and you should not be guessing at which parts of it might have survived that". I know it seems like this could conceivably be correct, but our experience with attempts to fix it up in other ways was that it always ended up resulting in very weird and incomprehensible corruption. -s
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#142853): https://lists.openembedded.org/g/openembedded-core/message/142853 Mute This Topic: https://lists.openembedded.org/mt/77174127/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
