Re: automount doesn't work without GPT table

[Sascha Hauer <s.hauer@pengutronix.de>]

On Fri, Feb 28, 2025 at 09:06:55AM +0300, Alexander Shiyan wrote:
> Hello Sascha.
> 
> 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.

Anyway, maybe we can do better by just mounting the partition to its
standard location the autmount would use anyway and just create a
symlink from /boot to /mnt/mmc1.0. I just sent a patch for this, you
could give it a try.

Sascha

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |