On 20 January 2018 at 12:00, Anton Aylward <opensuse@antonaylward.com> wrote:
So, yes, for me /var is a separate mountable file system. You need all those "parts". What goes in them is, well 'data', but it is 'variable data' such as the databases -- and of course the spool and the logs :-)
Whether you let BtrFS implement them as subdivisions -- subvolumes -- of the single volume or implement them as a separate file system is a decision on your part. As they say "YMMV". You really need to make this decision at install time; trying to 'fix it up' afterwards is a !PAIN!. BTDT.
On any openSUSE version before Tumbleweed 20180117 or Leap 15 then your above advice is not sensible. Treating /var as a separate mountable filesystem, be it as a partition, subvolume, or separate disk, will result in a broken system in the event of using snapper to rollback your system This is primarily because the rpm database used to record which packages are installed on your system is located in /var/lib/rpmdb Therefore rolling back to a point where you had a different set of packages installed will lead to the rpm database still thinking it had your pre-rollback packages installed That's a broken system. There are also other examples, such as the fillup-templates used to popular /etc/sysconfig, which are also located in /var/adm/fillup-templates until recently. So, sure, NOW, in a freshly installed Tumbleweed and SOON in Leap users will be able to treat /var as a separate mountable filesystem without system-breaking consequences, but for the majority of openSUSE's current users it's essential for the integrity of their system that they do NOT treat /var as a separate mountable filesystem when using btrfs, snapshots, and rollback. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org