From: Anton Mikanovich <amikan@ilbers.de>
To: Jan Kiszka <jan.kiszka@siemens.com>,
isar-users@googlegroups.com, Baurzhan Ismagulov <ibr@ilbers.de>
Subject: Re: [PATCH v2 3/5] rootfs: Unmount rootfs mounts if not needed
Date: Fri, 13 Aug 2021 19:27:48 +0300 [thread overview]
Message-ID: <e28de0a1-f48b-3e99-5a91-08ca5cf2a7fe@ilbers.de> (raw)
In-Reply-To: <637cb0c9-750f-b95e-e216-4d8daf957d55@siemens.com>
12.08.2021 12:25, Jan Kiszka wrote:
> On 12.08.21 11:09, Anton Mikanovich wrote:
>
>> Does this and
>> https://groups.google.com/d/msgid/isar-users/87cef6ee-411c-b611-4fb4-3957573d9455%40siemens.com
>> have happened on CI inside docker? Let me look into this issue anyway.
> Yes, in gitlab-ci. That's how we are testing because that's Isar is
> generally used.
>
> Jan
>
Ok, I've reproduced the issue inside both docker and chroot environment.
Have added some additional debug, hope it will help to find the reason.
From the first view it looks pretty much like the issue which forced
Isar to use lazy unmounts (it was never reproduced in Jenkins before).
Will continue investigation to find the real root cause.
--
Anton Mikanovich
Promwad Ltd.
External service provider of ilbers GmbH
Maria-Merian-Str. 8
85521 Ottobrunn, Germany
+49 (89) 122 67 24-0
Commercial register Munich, HRB 214197
General Manager: Baurzhan Ismagulov
next prev parent reply other threads:[~2021-08-13 16:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-21 14:58 [PATCH v2 0/5] isar: Rebuild mount logic Anton Mikanovich
2021-04-21 14:58 ` [PATCH v2 1/5] dpkg: Make mount buildroot reliable Anton Mikanovich
2021-04-21 14:58 ` [PATCH v2 2/5] buildchroot: Unmount buildchroot if not needed Anton Mikanovich
2021-04-21 14:58 ` [PATCH v2 3/5] rootfs: Unmount rootfs mounts " Anton Mikanovich
2021-08-12 5:39 ` Jan Kiszka
2021-08-12 9:09 ` Anton Mikanovich
2021-08-12 9:25 ` Jan Kiszka
2021-08-13 16:27 ` Anton Mikanovich [this message]
2021-08-15 19:05 ` Jan Kiszka
2021-04-21 14:58 ` [PATCH v2 4/5] wic: Unmount dirs after usage Anton Mikanovich
2021-04-21 14:58 ` [PATCH v2 5/5] events: Warn if mounted paths left Anton Mikanovich
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=e28de0a1-f48b-3e99-5a91-08ca5cf2a7fe@ilbers.de \
--to=amikan@ilbers.de \
--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