From: Adam Trhon <adam.trhon@tbs-biometrics.com>
To: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
Cc: "kernelnewbies@kernelnewbies.org" <kernelnewbies@kernelnewbies.org>
Subject: Re: Why is my block device busy?
Date: Fri, 24 Jan 2020 09:36:06 +0000 [thread overview]
Message-ID: <20200124103603.1eb983ac@loki02> (raw)
In-Reply-To: <32873.1579629041@turing-police>
Hello,
thank you, I figured out that the partition is mounted in initramfs and
not unmounted before the main system is started. When I manually unmount
the partition in initramfs, the problem goes away.
On Tue, 21 Jan 2020 12:50:41 -0500
"Valdis Klētnieks" <valdis.kletnieks@vt.edu> wrote:
> You should also check with 'cat /proc/mounts'.
I checked and it is not there.
> > Next I modified the ext driver to print stack when mounting, and I got:
> >
> > Call Trace:
> > ? ext4_calculate_overhead+0x520/0x520
> > mount_bdev+0x15a/0x180
>
> Looks like what I'd expect to see when in the mount syscall. What were
> you expecting to see here?
I expected the mount to be done by kernel itself, as I forgot about
initramfs, and that the stack trace would point me to the procedure that
does it in the kernel. Wrong guess :)
One more question, since I have another project that seldomly behaves
similarly, and I have had no luck with diagnostics so far. Is there a
way how to detect this problem (partition mounted, but not shown in
/proc/mounts) from the main system?
Thank you and best regards
Adam
--
Ing. Adam Trhoň, Software Engineer
Touchless Biometric Systems s.r.o. |
Palackého třída 180/44 | 61200 Brno | CZECH REPUBLIC |
Mobile: +42(0) 721 565 113 | tbs-biometrics.cz
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
prev parent reply other threads:[~2020-01-24 9:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-20 12:51 Why is my block device busy? Adam Trhon
2020-01-21 17:50 ` Valdis Klētnieks
2020-01-24 9:36 ` Adam Trhon [this message]
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=20200124103603.1eb983ac@loki02 \
--to=adam.trhon@tbs-biometrics.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=valdis.kletnieks@vt.edu \
/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;
as well as URLs for NNTP newsgroup(s).