mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Alexander Shiyan <eagle.alexander923@gmail.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: automount doesn't work without GPT table
Date: Fri, 28 Feb 2025 11:18:44 +0300	[thread overview]
Message-ID: <CAP1tNvTG-Na4pCD0qqh=hm647=UkQ7CzEFFHztgzHcq3m1bh=w@mail.gmail.com> (raw)
In-Reply-To: <Z8FuOsc_Eg-p6zCJ@pengutronix.de>

Hello.

> > The error occurs in the cdev_mount_default() function.
> > cdev_get_mount_path() returns "/boot".
> > And indeed, the partition is mounted here for some reason...
> > I don't understand yet why this happens.
> >
> > barebox@Mega-Milas Informer SAMA5D2:/ mount
> > none on / type ramfs
> > none on /dev type devfs
> > /dev/mmc1.0 on /boot type fat
> >
> > Update:
> > I found that this happens if the CONFIG_OF_BAREBOX_ENV_IN_FS option is used.
> > When disabled, mounting occurs as expected, but in this case I cannot
> > use environments from a file from a partition on the SD card.
> > It is not yet clear how to get out of this situation...
>
> Ok, so the partition is already mounted for the environment to /boot, so
> you get -EBUSY when trying to automount it somewhere else.
>
> The question arises why you want to access it via automount when you
> already mounted it for your environment.

Mounting the FULL partition with the environment file to /boot was a
surprise to me :)
I just expected the usual behavior of the automount command.

Thanks!



      reply	other threads:[~2025-02-28  8:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-27  6:37 Alexander Shiyan
2025-02-27 17:00 ` Sascha Hauer
2025-02-28  6:06   ` Alexander Shiyan
2025-02-28  8:05     ` Sascha Hauer
2025-02-28  8:18       ` Alexander Shiyan [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='CAP1tNvTG-Na4pCD0qqh=hm647=UkQ7CzEFFHztgzHcq3m1bh=w@mail.gmail.com' \
    --to=eagle.alexander923@gmail.com \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@pengutronix.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