public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Arnis" <arnis.juraga@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: sstate cache SSTATE_PKG generation will silently fail, if hardlinking is not supported on the file system #bitbake
Date: Thu, 15 Sep 2022 16:05:14 -0700	[thread overview]
Message-ID: <2xfY.1663283114373399868.FjIK@lists.openembedded.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 805 bytes --]

Hi,

I have faced a problem today that sstate-cache `${SSTATE_PKG}` generation will silently fail on the file systems no supporting hard linking.
I've faced this problem on cloud-based Kubernetes cluster, where persistent volume is mounted to Docker containers as shared sstate-cache location.

Because of https://git.openembedded.org/ openembedded-core/commit/?id= 552197a0c4c9f75a9177c00b197ea9 1296ed9fc4 ( https://git.openembedded.org/openembedded-core/commit/?id=552197a0c4c9f75a9177c00b197ea91296ed9fc4 ) change

+ ln $TFILE ${SSTATE_PKG} || true

this will leave sstate folder with only `*...tar.zst.siginfo` files generated, but no "*...tar.zst"

As a temporary solution, I have replaced it with

+ cp $TFILE ${SSTATE_PKG}

which obviously is not ideal.

What would you suggest?

[-- Attachment #2: Type: text/html, Size: 2188 bytes --]

             reply	other threads:[~2022-09-15 23:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-15 23:05 Arnis [this message]
2022-09-16  9:26 ` [OE-core] sstate cache SSTATE_PKG generation will silently fail, if hardlinking is not supported on the file system #bitbake Richard Purdie

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=2xfY.1663283114373399868.FjIK@lists.openembedded.org \
    --to=arnis.juraga@gmail.com \
    --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