From: "André Draszik" <git@andred.net>
To: openembedded-core@lists.openembedded.org
Subject: Re: broken sstate archives
Date: Mon, 12 Nov 2018 12:56:52 +0000 [thread overview]
Message-ID: <20181112125653.21157-1-git@andred.net> (raw)
In-Reply-To: <09487c1d7e9d9a2cf0c60883ad209712c2d31dc2.camel@andred.net>
As a follow-up and as a reference for the future - having done countless
builds I am confident enough that a kernel update solved the problem:
- linux (Debian 9) versions 4.9.110-3+deb9u6 and 4.9.110-3+deb9u5 both
exhibit the problem
- 4.18.6-1~bpo9+1 doesn't
Something must have gone into the btrfs driver to fix the issue. I didn't
really spend the time to try and find the relevant commit.
For reference, I am also sending my hackish patch to poky to detect
the error case early, which (tries) to detect the broken archive, and
simply runs tar again.
Thanks Richard for all your inputs.
Cheers,
Andre'
next prev parent reply other threads:[~2018-11-12 12:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-30 15:45 broken sstate archives André Draszik
2018-10-30 16:49 ` Richard Purdie
2018-11-01 12:22 ` André Draszik
2018-11-01 13:07 ` richard.purdie
2018-11-12 12:56 ` André Draszik [this message]
2018-11-12 12:56 ` [DONT-MERGE] sstate: add hack to detect sstate archive compression failures André Draszik
2018-11-12 14:07 ` broken sstate archives 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=20181112125653.21157-1-git@andred.net \
--to=git@andred.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