On 07/15/2015 08:14 PM, Carlos E. R. wrote:
On 2015-07-15 20:07, Anton Aylward wrote:
On 07/15/2015 11:09 AM, Istvan Gabor wrote:
1. Configure your snapshots properly. ... There are good reasons to have the rootFS (and hence quite possibly the initrd) as small as practical. There are EXCELLENT reasons to have /boot on a separate partition, not least of all when you have to performs a recovery the times the rootFS goes haywire.
You need /boot and / in the same partition to use on of the most useful features of btrfs and snapshots: be able to boot the system as it was before an update that went fubar.
I see no purpose in keeping /boot as part of the RootFS under a BtrFS file system. I do see a great deal of utility in having it as a small (comparatively speaking on a 1T drive for example) as an ext[234] partition. It makes life a LOT simpler when thing go pear shaped and the BtrFS goes into some unrecoverable state. I *do* understand about snapshots and their use as 'backup'. But the only cse I cn see where having a /boot where you can't get to a previous version is if you configure /etc/zypp/zypp.conf not to store multiversion, that is to store one and only oncer version of the bootable kernel. I have multiversion.kernels = oldest,latest,latest-1,latest-2,running for that entry, which is, perhaps, overkill. However none of this has to do with the very basic matter of "Configure your snapshots properly". As I said. its a pity that snapper can't have exclusion lists like rsync. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org