From: "Hombourger, Cedric" <Cedric_Hombourger@mentor.com>
To: Jan Kiszka <jan.kiszka@siemens.com>,
"Maxim Yu. Osipov" <mosipov@ilbers.de>,
isar-users <isar-users@googlegroups.com>
Subject: RE: [PATCH 0/3] umount fixes and cleanups
Date: Wed, 5 Dec 2018 12:31:38 +0000 [thread overview]
Message-ID: <32728b629b094f79ad589524d097ffb2@svr-ies-mbx-02.mgc.mentorg.com> (raw)
In-Reply-To: <02edaac4-fc2d-44ea-6471-52ad8fc3d421@siemens.com>
I was able to use the following work-around for your test-case:
# run the following command until all mounts are gone
umount $(mount |grep $PWD/my-mnt|awk '{print $3}')
umount -R or -l indeed failed
Cedric
-----Original Message-----
From: Jan Kiszka [mailto:jan.kiszka@siemens.com]
Sent: Wednesday, December 5, 2018 3:15 PM
To: Maxim Yu. Osipov <mosipov@ilbers.de>; isar-users <isar-users@googlegroups.com>
Cc: Hombourger, Cedric <Cedric_Hombourger@mentor.com>
Subject: Re: [PATCH 0/3] umount fixes and cleanups
On 05.12.18 12:12, Maxim Yu. Osipov wrote:
> On 12/5/18 12:29 PM, Jan Kiszka wrote:
>> Patches related to resolving the pending CI issues as well as
>> simplifying the umounts used during cleanup.
>
> Tried to run in patch queue:
>
> 027b7cf Remove redundant recursive umounts
> c1bdc33 isar-events: Improve umount handler
> b354273 ci: Wait for bitbake worker to finish before deleting
> artifacts
> 9cf29e6 isar-bootstrap: Fix and cleanup bind mounting
> b354026 isar-image: umount base-apt when doing offline build e965c0d
> gitlab-ci: Switch to ci_build.sh ...
>
> After execution of problematic test case (I rebooted PC and executed
> steps in clean tree):
>
> my stretch Debian system was entered into unusable state as many
> important mounts were disappeared (see log of mount points before and
> after execution of last command attached).
OK, so I took the time and extracted the root cause. We may see a Debian 4.9 kernel bug here:
# mkdir my-mnt
# mount --rbind /sys my-mnt
# mount --make-rslave my-mnt
# umount {-R,-l,-R -l} my-mnt
# rmdir my-mnt
rmdir: failed to remove 'my-mnt': Device or resource busy
This works fine on my Leap 15.0 kernel (4.12) as well as the 4.4 kernel (Ubuntu) used on our CI server.
*This* is information we can base commits on. Also, we can file a bug against Debian with this. Could you do that (keep my in CC)?
Thanks,
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2018-12-05 12:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-05 9:29 Jan Kiszka
2018-12-05 9:29 ` [PATCH 1/3] ci: Wait for bitbake worker to finish before deleting artifacts Jan Kiszka
2018-12-05 9:52 ` Hombourger, Cedric
2018-12-05 9:59 ` Maxim Yu. Osipov
2018-12-05 10:04 ` Jan Kiszka
2018-12-05 9:29 ` [PATCH 2/3] isar-events: Improve umount handler Jan Kiszka
2018-12-05 9:29 ` [PATCH 3/3] Remove redundant recursive umounts Jan Kiszka
2018-12-05 11:12 ` [PATCH 0/3] umount fixes and cleanups Maxim Yu. Osipov
2018-12-05 11:32 ` Hombourger, Cedric
2018-12-05 12:14 ` Jan Kiszka
2018-12-05 12:31 ` Hombourger, Cedric [this message]
2018-12-05 12:35 ` Jan Kiszka
2018-12-05 12:48 ` Hombourger, Cedric
2018-12-05 12:54 ` Jan Kiszka
2018-12-05 14:26 ` Maxim Yu. Osipov
2018-12-05 14:52 ` Jan Kiszka
2018-12-05 23:08 ` Jan Kiszka
2018-12-07 13:46 ` Maxim Yu. Osipov
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=32728b629b094f79ad589524d097ffb2@svr-ies-mbx-02.mgc.mentorg.com \
--to=cedric_hombourger@mentor.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
--cc=mosipov@ilbers.de \
/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