Bug 15283 - encounter error(create archive failed: cpio: write failed) when build iso-codes
Summary: encounter error(create archive failed: cpio: write failed) when build iso-codes
Status: RESOLVED WORKSFORME
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: multimedia (show other bugs)
Version: 4.0.14
Hardware: x86 Multiple
: Medium+ normal
Target Milestone: 5.0 M1
Assignee: sucrehu
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2023-11-17 08:17 UTC by sucrehu
Modified: 2024-01-11 15:49 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Don't know


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description sucrehu 2023-11-17 08:17:27 UTC
1. install essential components according below link.
https://docs.yoctoproject.org/4.0.14/ref-manual/system-requirements.html#supported-linux-distributions
2. according below link to build the original yocto Kirkstone project, then got the error log(create archive failed: cpio: write failed - Resource temporarily unavailable).
https://docs.yoctoproject.org/4.0.14/brief-yoctoprojectqs/index.html
3. It also got the error log when perform command(bitbake iso-codes).

build server info:
lsb_release -a
LSB Version:    core-11.1.0ubuntu4-noarch:security-11.1.0ubuntu4-noarch
Distributor ID: Ubuntu
Description:    Ubuntu 22.04.3 LTS
Release:        22.04
Codename:       jammy

error log as below:
error: create archive failed: cpio: write failed - Resource temporarily unavailable
error: create archive failed: cpio: write failed - Resource temporarily unavailable

error: create archive failed: cpio: write failed - Resource temporarily unavailable
error: create archive failed: cpio: write failed - Resource temporarily unavailable
error: create archive failed: cpio: write failed - Resource temporarily unavailable
error: create archive failed: cpio: write failed - Resource temporarily unavailable

error: create archive failed: cpio: write failed - Resource temporarily unavailable
error: create archive failed: cpio: write failed - Resource temporarily unavailable

error: create archive failed: cpio: write failed - Resource temporarily unavailable

error: create archive failed: cpio: write failed - Resource temporarily unavailable
error: create archive failed: cpio: write failed - Resource temporarily unavailable
error: create archive failed: cpio: write failed - Resource temporarily unavailable
error: create archive failed: cpio: write failed - Resource temporarily unavailable
error: create archive failed: cpio: write failed - Resource temporarily unavailable
error: create archive failed: cpio: write failed - Resource temporarily unavailable

error: create archive failed: cpio: write failed - Resource temporarily unavailable

error: create archive failed: cpio: write failed - Resource temporarily unavailable

Wrote: /home/data/xxxxx/yocto_poky/poky/build/tmp/work/all-poky-linux/iso-codes/4.15.0-r0/deploy-rpms/noarch/iso-codes-locale-ba-4.15.0-r0.noarch.rpm

Wrote: /home/data/xxxx/yocto_poky/poky/build/tmp/work/all-poky-linux/iso-codes/4.15.0-r0/deploy-rpms/noarch/iso-codes-locale-tl-4.15.0-r0.noarch.rpm

....................
Comment 1 Ross Burton 2023-11-23 16:23:03 UTC
Is this inside a container or some unusual file system?  cpio just does very conventional file operations so getting "resource temporarily unavailable" is very odd.

It feels like you're doing a build over NFS, or in a container with a network-backend filesystemm.  If this is the case we should be detecting and refusing to work, for reasons like this.
Comment 2 Ross Burton 2024-01-11 15:49:25 UTC
Closing as works-for-me: if this continues to be a problem please re-open with the details requested.