Re: [HELP] tmp/work/debian-bullseye-arm64/isar-image-base-qemuarm64/1.0-r0/mnt/rootfs: target is busy

[Jan Kiszka <jan.kiszka@siemens.com>]

On 26.02.24 11:26, 'cedric.hombourger@siemens.com' via isar-users wrote:
> 
> Hello,
> 
> Seeing some sporadic failures with the test suite (but also with builds
> of our Isar-based product) when rootfs_install_sstate_prepare gets
> executed:
> 
> DEBUG: Executing shell function rootfs_install_sstate_prepare
> umount: /home/sutlej/isar/build/tmp/work/debian-bullseye-arm64/isar-
> image-base-qemuarm64/1.0-r0/mnt/rootfs: target is busy.
> WARNING: exit code 32 from a shell command. 
> 
> What's special about the machine I am running the builds on is that
> /proc/cpuinfo reports 64 processors hence builds get massively
> parallelized
> 
> I wasn't able to get to the bottom of this issue and understand why the
> bind mount is busy since rootfs_install_sstate_prepare creates, uses
> and removes that bind mount in the same function.
> 
> As a work-around, a lazy umount could be used but that annoys me as I'd
> like to understand what could cause this. Any ideas?
> 

This is indeed weird: ${WORKDIR}/mnt/rootfs is only mounted by
rootfs_install_sstate_prepare in vanilla isar, and that happens under
isar.lock - close to impossible to have a race here. But did you check
in your recipes on top (assuming the issue is not reproducible for you
with vanilla isar alone) that there is no other usage of
${WORKDIR}/mnt/rootfs, possibly unlocked then?

Jan

-- 
Siemens AG, Technology
Linux Expert Center