From: "'Schultschik, Sven' via isar-users" <isar-users@googlegroups.com>
To: "amikan@ilbers.de" <amikan@ilbers.de>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>,
"Kiszka, Jan" <jan.kiszka@siemens.com>,
"cedric.hombourger@siemens.com" <cedric.hombourger@siemens.com>,
"ibr@ilbers.de" <ibr@ilbers.de>,
"ctngkhn@gmail.com" <ctngkhn@gmail.com>
Cc: "Gupta, Sameer" <sameer.gupta@siemens.com>
Subject: Re: schroot umount target is busy
Date: Wed, 6 Aug 2025 08:28:32 +0000 [thread overview]
Message-ID: <9addcf0b1014dd775fe85d2fd66a877af39b9e36.camel@siemens.com> (raw)
In-Reply-To: <8a611b46-370e-46f4-8ebc-725f6dbfbef5@ilbers.de>
[-- Attachment #1: Type: text/plain, Size: 3274 bytes --]
Hello everyone,
I saw that there where several patches in the past and it seemed
better, but we're phasing again issues with this problem in the CI/CD
pipeline.
We are currently on the 0.10 isar version.
2025-08-05 19:44:23 - INFO - | update-alternatives: using /bin/mt-
gnu to provide /bin/mt (mt) in auto mode
2025-08-05 19:44:23 - INFO - | Processing triggers for man-db
(2.11.2-2) ...
2025-08-05 19:44:23 - INFO - | 606473 blocks
2025-08-05 19:44:23 - INFO - | E: 10mount: umount:
/run/schroot/mount/isar-builder-422f34fc-0228-432e-89c2-dcb36197702b-
388848-c8bce6c5-6eb2-444d-bafc-b94069fd47dc/home/builder/audis-lpe-
rescue-debug-lpe9403-std/deploy: target is busy.
2025-08-05 19:44:23 - INFO - | E: 10mount: umount:
/run/schroot/mount/isar-builder-422f34fc-0228-432e-89c2-dcb36197702b-
388848-c8bce6c5-6eb2-444d-bafc-b94069fd47dc: target is busy.
2025-08-05 19:44:23 - INFO - | E: 10mount: rmdir: failed to remove
'/var/run/schroot/mount/isar-builder-422f34fc-0228-432e-89c2-
dcb36197702b-388848-c8bce6c5-6eb2-444d-bafc-b94069fd47dc': Device or
resource busy
2025-08-05 19:44:23 - INFO - | E: isar-builder-422f34fc-0228-432e-
89c2-dcb36197702b-388848-c8bce6c5-6eb2-444d-bafc-b94069fd47dc: Chroot
setup failed: stage=setup-stop
2025-08-05 19:44:23 - INFO - NOTE: recipe rescue-debug-1.0-r0: task
do_image_cpio: Failed
2025-08-05 19:44:23 - ERROR - ERROR: Task (/build/../work/lpe9403-
base/recipes-core/images/audis-lpe-rescue-debug.bb:do_image_cpio)
failed with exit code '1'
2025-08-05 21:06:41 - INFO - | Processing triggers for man-db
(2.11.2-2) ...
2025-08-05 21:06:41 - INFO - | tune2fs 1.47.0 (5-Feb-2023)
2025-08-05 21:06:41 - INFO - | E: 10mount: umount:
/run/schroot/mount/isar-builder-7acbebe3-8b26-4def-abd5-a48d19ef4673-
1166849-61509bf3-3372-41e4-ba7d-1d13acb5fa42: target is busy.
2025-08-05 21:06:41 - INFO - | E: 10mount: rmdir: failed to remove
'/var/run/schroot/mount/isar-builder-7acbebe3-8b26-4def-abd5-
a48d19ef4673-1166849-61509bf3-3372-41e4-ba7d-1d13acb5fa42': Device or
resource busy
2025-08-05 21:06:41 - INFO - | E: isar-builder-7acbebe3-8b26-4def-
abd5-a48d19ef4673-1166849-61509bf3-3372-41e4-ba7d-1d13acb5fa42: Chroot
setup failed: stage=setup-stop
2025-08-05 21:06:41 - INFO - NOTE: recipe image-debug-1.0-r0: task
do_image_ext4: Failed
2025-08-05 21:06:41 - ERROR - ERROR: Task (/build/../repo/recipes-
core/images/audis-lpe-image-debug.bb:do_image_ext4) failed with exit
code '1'
bg Sven
On Fri, 2024-07-12 at 10:04 +0300, Anton Mikanovich wrote:
> Hello Gökhan,
>
> I've found an issue with isar-apt usage without lock protection in
> deb_dl_dir_export and imager_run implementations. This can influence
> on
> umount
> issues you've observed, so please try the fix from patchset:
>
> [PATCH 0/2] Protect isar-apt usages in shell
>
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/9addcf0b1014dd775fe85d2fd66a877af39b9e36.camel%40siemens.com.
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 11633 bytes --]
next prev parent reply other threads:[~2025-08-06 8:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-05 8:47 Schultschik, Sven
2024-06-05 8:55 ` Jan Kiszka
2024-07-08 14:17 ` Gökhan Çetin
2024-07-08 15:13 ` 'Jan Kiszka' via isar-users
2024-07-09 6:28 ` Gökhan Çetin
2024-07-09 6:48 ` Anton Mikanovich
2024-07-12 7:04 ` Anton Mikanovich
2024-08-06 8:02 ` Anton Mikanovich
2024-08-06 8:19 ` Gökhan Çetin
2025-08-06 8:28 ` 'Schultschik, Sven' via isar-users [this message]
2024-07-09 6:52 ` 'cedric.hombourger@siemens.com' via isar-users
2024-07-09 10:27 ` 'Jan Kiszka' via isar-users
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=9addcf0b1014dd775fe85d2fd66a877af39b9e36.camel@siemens.com \
--to=isar-users@googlegroups.com \
--cc=amikan@ilbers.de \
--cc=cedric.hombourger@siemens.com \
--cc=ctngkhn@gmail.com \
--cc=ibr@ilbers.de \
--cc=jan.kiszka@siemens.com \
--cc=sameer.gupta@siemens.com \
--cc=sven.schultschik@siemens.com \
/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