On 13 September 2017 at 23:08, Seebs <[email protected]> wrote: > On Wed, 13 Sep 2017 22:50:32 +0200 > Martin Jansa <[email protected]> wrote: > > > inode mismatch: > > '/OE/build/oe-core/tmp-glibc/work/core2-64-oe-linux/ > systemd/1_234-r0/recipe-sysroot/etc/group' > > ino 29361846 in db, 29361904 in request. > > Just to be clear about this: > > This is at least potentially an Actual Problem. It's probably not a > good idea to habitually ignore these. A thing like this happening means > that, at some point: > > 1. Something created etc/group, and it got inode 29361846 recorded in > the database. > 2. Something deleted etc/group, and did NOT record this to the database. > 3. Something created etc/group, with inode 29361904. > > It's possible that the thing creating etc/group didn't record it to the > database, and something else just referred to it later (like a stat > call), or that this was generated by the request creating the entry. > > Either way, it means changes were made to a pseudo-managed hunk of > filesystem without pseudo knowing about it, and that is generally bad.
I just applied this patch and got an identical hit in systemd, which makes me think that the useradd class (maze of code that it is) is causing this instance. Ross
-- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
