Comment 6 for bug 1926137

Revision history for this message
Ryan Harper (raharper) wrote : Re: [Bug 1926137] Re: Error when starting copy to disk due to processes accessing /var/log

> I think all curtin can do here is fail more gracefully, if anything --
> there's not going to be a sensible way to unmount a partition that has
> /var/log on it.

Agreed. Curtin could certainly attempt to umount it and if that succeeded
we could proceed otherwise we'd at least fail early showing that we
couldn't
umount the device that was part of the config.

On Mon, May 3, 2021 at 5:55 PM Michael Hudson-Doyle <
<email address hidden>> wrote:

> I think all curtin can do here is fail more gracefully, if anything --
> there's not going to be a sensible way to unmount a partition that has
> /var/log on it.
>
> Maybe casper should only automount a writable filesystem from the same
> media as the livefs was found? That probably breaks some other use
> cases, but might be less surprising all in all.
>
> --
> You received this bug notification because you are subscribed to
> subiquity.
> Matching subscriptions: subiquity-bugs
> https://bugs.launchpad.net/bugs/1926137
>
> Title:
> Error when starting copy to disk due to processes accessing /var/log
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/subiquity/+bug/1926137/+subscriptions
>