From: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>
To: "Moessbauer, Felix" <felix.moessbauer@siemens.com>
Cc: "ubely@ilbers.de" <ubely@ilbers.de>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>,
"Kiszka, Jan" <jan.kiszka@siemens.com>,
"Schild, Henning" <henning.schild@siemens.com>
Subject: Re: [PATCH v3 0/5] Improving apt cache
Date: Mon, 30 Jan 2023 15:16:57 +0100 [thread overview]
Message-ID: <CAJGKYO6tAaPWgDwygUf-P2+43aRtc7w2KjC1tAMEEaL=UfUb7g@mail.gmail.com> (raw)
In-Reply-To: <cac52c2157515ae646f5a04a80a3d77beeb11104.camel@siemens.com>
On Mon, 30 Jan 2023 at 09:45, Moessbauer, Felix
<felix.moessbauer@siemens.com> wrote:
>
> On Fri, 2023-01-20 at 08:31 +0100, Uladzimir Bely wrote:
> > Currently, apt cache (e.g. `var/cache/apt/archives`) import and
> > export
> > functions are not optimal. Multiple files are copied from global
> > DL_DIR to package WORKDIR, increasing disk IO and space needed.
> >
> > Also, various chroots (bootstrap, buildchroot, sbuild chroot) include
> > their apt caches to sstate cache files.
> >
> > This patchset switches to hardlinks instead of copies and removes apt
> > cache from bootstrapped images ans sstate caches.
>
> I just saw that this pattern does NOT work in case the cache is on a
> different filesystem. This unfortunately is the case for all CI systems
> with locally mounted caches, as well as for kas-container builds with
> DL_DIR outside the KAS_WORK_DIR.
>
> In short: This breaks a LOT of use-cases.
> I'm really sorry that we only found that by know.
> But we definitely need a different solution.
>
> Example output:
> 2023-01-30 08:38:51 - INFO - | ln: failed to create hard link
> '/builds/iiot-edge-device/foo/meta-iot2050-pg2-
> foo/build/tmp/work/debian-bullseye-amd64/isar-bootstrap-target/1.0-
> r0/rootfs/var/cache/apt/archives/gcc-arm-linux-gnueabihf_4%3a10.2.1-
> 1_arm64.deb' => '/local-cache/meta-iot2050-pg2-
> foo/downloads/deb/debian-bullseye/gcc-arm-linux-gnueabihf_4%3a10.2.1-
> 1_arm64.deb': Invalid cross-device link
>
One more thing: as shown to Uladzimir, as long as the source of two
different mount points (not filesystems) exists on the same
filesystem, then lp -P complains but for some reason it works. I do
not grant that it works in any case but it works enough for which a
2>/dev/null makes the building complete and no one notices. So, if it
does not build, that's an issue. If it completes the build despite the
stderr messages, we are lucky. However, if confirmed - this weird
behaviour - is out of the standard, so being lucky is not enough in
the long run.
Best regards, R-
prev parent reply other threads:[~2023-01-30 14:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-20 7:31 Uladzimir Bely
2023-01-20 7:31 ` [PATCH v3 1/5] Clean apt cache from debootstrapped rootfs dirs Uladzimir Bely
2023-01-20 7:31 ` [PATCH v3 2/5] Use hardlinks in deb-dl-dir import/export Uladzimir Bely
2023-01-20 7:31 ` [PATCH v3 3/5] Exclude apt cache from sstate caches Uladzimir Bely
2023-01-20 7:31 ` [PATCH v3 4/5] Use symlinks when importing debian packages to sbuild chroot Uladzimir Bely
2023-01-20 7:31 ` [PATCH v3 5/5] Lightweight copy of rootfs directories if possible Uladzimir Bely
2023-01-20 13:04 ` [PATCH v3 0/5] Improving apt cache Moessbauer, Felix
2023-01-21 4:12 ` Roberto A. Foglietta
2023-01-24 7:38 ` Uladzimir Bely
2023-01-30 8:45 ` Moessbauer, Felix
2023-01-30 9:56 ` Roberto A. Foglietta
2023-01-30 10:04 ` Roberto A. Foglietta
2023-01-30 10:45 ` Henning Schild
2023-01-30 12:24 ` Roberto A. Foglietta
2023-01-30 14:16 ` Roberto A. Foglietta [this message]
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='CAJGKYO6tAaPWgDwygUf-P2+43aRtc7w2KjC1tAMEEaL=UfUb7g@mail.gmail.com' \
--to=roberto.foglietta@gmail.com \
--cc=felix.moessbauer@siemens.com \
--cc=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
--cc=ubely@ilbers.de \
/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