Re: Setting up /boot when it is not a separate partition
- From: Colin Walters <walters verbum org>
- To: Chris Murphy <lists colorremedies com>, ostree-list gnome org
- Subject: Re: Setting up /boot when it is not a separate partition
- Date: Tue, 21 Jul 2015 15:19:54 -0400
On Tue, Jul 21, 2015, at 03:13 PM, Chris Murphy wrote:
How does ostree/rpm-ostree handle many trees where there are too many kernels+initramfses for separate /boot to hold? On Fedora in particular, with frequent kernel updates, this seems like a problem.
Keep in mind that by default, only a maximum of 3 deployments is transiently present per OS, and default 2 persistent (in the middle of upgrading, you have 2, plus the new one, then the old one will be GC'd). This is of course up to the client tools - OSTree supports as many deployments as you have space, but it's what at least /usr/bin/rpm-ostree and /usr/bin/ostree do.
But if `/boot` gets full, the filesystem will report `ENOSPC`, and the new deployment will fail, leaving your current system untouched. `ostree admin cleanup` will delete any transiently created files.
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]