From: "'Florian Bezdeka' via isar-users" <isar-users@googlegroups.com>
To: isar-users@googlegroups.com, Anton Mikanovich <amikan@ilbers.de>,
Jan Kiszka <jan.kiszka@siemens.com>
Subject: Re: [PATCH] meta: Drop lazy and recursive unmounts
Date: Fri, 04 Oct 2024 09:28:15 +0200 [thread overview]
Message-ID: <143d65f425959b3510c96ae08f20791ea46655d5.camel@siemens.com> (raw)
In-Reply-To: <Zv6sLwXgXm1p5yTw@abai.m.ilbers.de>
On Thu, 2024-10-03 at 16:37 +0200, Baurzhan Ismagulov wrote:
> Hello Florian,
>
> On 2024-10-01 13:59, Florian Bezdeka wrote:
> > I scanned the logs and searched for /dev mounts. Typical example:
> >
> > tmp/work/debian-bookworm-amd64/isar-exclude-docs/0.2.2-r0/temp/log.do_dpkg_build.18089
> > 521:devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=666)
> > 522:tmpfs on /dev/shm type tmpfs (rw,relatime,inode64)
>
> We'll address the patches with priority. Could you please provide 1. the output
> of bitbake ... 2>&1 |tee bitbake.txt and 2. the related failed task
> log.do_build? Off-list if sensitive.
I already sent patches for fixing this issue. There is no failed task.
rootfs::do_rootfs_postprocess and rootfs::do_rootfs_install both call
rootfs::rootfs_do_mounts but never clean up.
In case the mounts are left behind I will run into "can not umount,
device still active" later.
>
>
> > At the end I still have one active /dev mount:
> > tmpfs on /builds/myproject/build/tmp/work/debian-bookworm-amd64/sbuild-chroot-target/1.0-r0/rootfs/dev type tmpfs (rw,nosuid,size=65536k,mode=755,inode64)
>
> Thanks for the info, this looks like an sbuild migration bug. Checking.
Reviewing patches should do it...
>
>
> With kind regards,
> Baurzhan
--
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/143d65f425959b3510c96ae08f20791ea46655d5.camel%40siemens.com.
next prev parent reply other threads:[~2024-10-04 7:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-19 10:41 Anton Mikanovich
2024-06-26 6:31 ` Uladzimir Bely
2024-08-28 13:05 ` 'Florian Bezdeka' via isar-users
2024-08-29 9:26 ` Anton Mikanovich
2024-08-29 12:26 ` 'Florian Bezdeka' via isar-users
2024-09-06 14:34 ` Anton Mikanovich
2024-10-01 11:59 ` 'Florian Bezdeka' via isar-users
2024-10-01 12:14 ` 'Jan Kiszka' via isar-users
2024-10-01 12:18 ` 'Florian Bezdeka' via isar-users
2024-10-01 12:28 ` 'Jan Kiszka' via isar-users
2024-10-03 14:37 ` Baurzhan Ismagulov
2024-10-04 7:28 ` 'Florian Bezdeka' via isar-users [this message]
2024-10-04 8:00 ` Uladzimir Bely
2024-10-04 8:16 ` 'Jan Kiszka' via isar-users
2024-10-10 4:33 ` 'Jan Kiszka' via isar-users
2024-10-10 9:43 ` Baurzhan Ismagulov
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=143d65f425959b3510c96ae08f20791ea46655d5.camel@siemens.com \
--to=isar-users@googlegroups.com \
--cc=amikan@ilbers.de \
--cc=florian.bezdeka@siemens.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