From: Seebs <seebs@seebs.net>
To: openembedded-core@lists.openembedded.org
Subject: Re: [RFC][PATCH] insane.bbclass: Add do_qa_pseudo function to check for common errors listed in pseudo.log
Date: Wed, 13 Sep 2017 17:08:30 -0500 [thread overview]
Message-ID: <20170913170830.6ac2b8bb@seebsdell> (raw)
In-Reply-To: <20170913205032.GD3288@jama>
On Wed, 13 Sep 2017 22:50:32 +0200
Martin Jansa <martin.jansa@gmail.com> 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.
-s
next prev parent reply other threads:[~2017-09-13 22:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-13 20:46 [RFC][PATCH] insane.bbclass: Add do_qa_pseudo function to check for common errors listed in pseudo.log Martin Jansa
2017-09-13 20:50 ` Martin Jansa
2017-09-13 22:08 ` Seebs [this message]
2017-09-13 22:28 ` Martin Jansa
2017-09-14 14:27 ` Seebs
2017-09-14 13:17 ` Burton, Ross
2017-09-13 22:09 ` Seebs
2017-09-14 14:53 ` Burton, Ross
2017-09-14 14:59 ` Seebs
2017-09-19 15:18 ` [RFC][PATCHv2] " Martin Jansa
2017-10-16 15:01 ` Martin Jansa
2017-10-16 15:10 ` Burton, Ross
2017-10-16 15:50 ` Martin Jansa
2017-12-19 16:09 ` Martin Jansa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170913170830.6ac2b8bb@seebsdell \
--to=seebs@seebs.net \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox