mail archive of the rauc mailing list
 help / color / mirror / Atom feed
From: Ladislav Michl <ladis@linux-mips.org>
To: rauc@pengutronix.de
Subject: Re: [RAUC] Failed to mount seed slot
Date: Tue, 7 May 2019 09:31:28 +0200	[thread overview]
Message-ID: <20190507073128.GA649@lenoch> (raw)
In-Reply-To: <20190506174409.GA23081@lenoch>

On Mon, May 06, 2019 at 07:44:09PM +0200, Ladislav Michl wrote:
> Hi there,
> 
> I'm using rauc with casync to update target system - it is symmetric rootfsA,
> rootfsB, scenario, so slots are defined as:
> [slot.rootfs.0]
> device=/dev/ubi0_0
> type=ubifs
> bootname=system0
> 
> [slot.rootfs.1]
> device=/dev/ubi0_1
> type=ubifs
> bootname=system1
> 
> Now system is booted with rootfs mounted read only which makes mounting seed
> slot fail:
> rauc[871]: Mounting /dev/ubi0_0 to use as seed
> rauc[871]: launching subprocess: mount -t ubifs /dev/ubi0_0 /run/rauc/rootfs.0
> rauc[871]: posix_spawn avoided (fd close requested) (child_setup specified) 
> rauc[871]: mount: /run/rauc/rootfs.0: /dev/ubi0_0 already mounted or mount point busy.
> 
> Here adding '-o ro' would quick fix it up (but break rw case, as options have to
> match), so it seems better to use bind mount as comment casync_extract_image
> function suggests, but do not see it code.
> 
> Am I missing anything?

So, whats still missing is a review of pull request #406 (Normalize device names
to find mounted slots) :)

Then determine_slot_states should properly fill slot's ext_mount_point and
casync_extract_image would then use it to bind mount seed slot.

And here's the tricky part. For device-less mount, volume to mount is specified
for example using ubiX_Y or ubiX:NAME syntax, so fix in #406 will fail in this
case.

A workaround is to add support to bootloader which will try to guess UBI
volume character device as seen by kernel.

Now it is time to make design decision: if rauc is going to suppport device-less
mounts this should be fixed (read: I'll provide a patch for review). Otherwise
I'll change a way bootloader passes root= option.

Thank you,
	ladis

_______________________________________________
RAUC mailing list

  reply	other threads:[~2019-05-07  7:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-06 17:44 Ladislav Michl
2019-05-07  7:31 ` Ladislav Michl [this message]
2019-05-07 15:49   ` Ladislav Michl
2019-05-07 17:59     ` Trent Piepho
2019-05-07 20:33       ` Ladislav Michl
2019-05-09 11:32         ` Ladislav Michl
2019-05-08  5:44       ` Ladislav Michl

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=20190507073128.GA649@lenoch \
    --to=ladis@linux-mips.org \
    --cc=rauc@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