public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Anton Mikanovich <amikan@ilbers.de>
To: "Gökhan Çetin" <ctngkhn@gmail.com>,
	isar-users <isar-users@googlegroups.com>,
	"Kiszka, Jan" <jan.kiszka@siemens.com>,
	"cedric.hombourger@siemens.com" <cedric.hombourger@siemens.com>,
	"Baurzhan Ismagulov" <ibr@ilbers.de>
Subject: Re: schroot umount target is busy
Date: Tue, 6 Aug 2024 11:02:48 +0300	[thread overview]
Message-ID: <a53a8580-854b-481c-a788-16fdab357e88@ilbers.de> (raw)
In-Reply-To: <8a611b46-370e-46f4-8ebc-725f6dbfbef5@ilbers.de>

12/07/2024 10:04, 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

Unfortunately this fix didn't help.
Even with it we've got the same issue (it looks like there is the first time
we've catched it in our CI):

ERROR: Task 
(mc:qemuarm-bullseye:/workspace/build-auto/isar_next/1324/meta-test/recipes-core/images/isar-image-ci.bb:do_image_ext4) 
failed with exit code '1'
E: 10mount: umount: 
/run/schroot/mount/isar-jenkins-0c03d5d2-da53-444c-93f6-fc9bdfafc290-2097734-1868b26c-f678-4e99-9e9a-360c7c05fcd3: 
target is busy.
E: 10mount: rmdir: failed to remove 
'/var/run/schroot/mount/isar-jenkins-0c03d5d2-da53-444c-93f6-fc9bdfafc290-2097734-1868b26c-f678-4e99-9e9a-360c7c05fcd3': 
Device or resource busy
E: 
isar-jenkins-0c03d5d2-da53-444c-93f6-fc9bdfafc290-2097734-1868b26c-f678-4e99-9e9a-360c7c05fcd3: 
Chroot setup failed: stage=setup-stop

-- 
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 on the web visit https://groups.google.com/d/msgid/isar-users/a53a8580-854b-481c-a788-16fdab357e88%40ilbers.de.

  reply	other threads:[~2024-08-06  8:03 UTC|newest]

Thread overview: 11+ 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 [this message]
2024-08-06  8:19             ` Gökhan Çetin
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=a53a8580-854b-481c-a788-16fdab357e88@ilbers.de \
    --to=amikan@ilbers.de \
    --cc=cedric.hombourger@siemens.com \
    --cc=ctngkhn@gmail.com \
    --cc=ibr@ilbers.de \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@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