David C. Rankin wrote:
The un-whitewashed version reads "Before 15, there were problems with btrfs".
I wouldn't phrase it like that. The issue is that you do not want to back up user/log data in system snapshots (as it would make them even larger). But you could not place whole /var in a subvolume because it still contained system- and version dependent stuff (like the rpm database). So point 1 was not an issue of btrfs, but only of system layout. This had been 'repaired' in Tumbleweed at some point, allowing to put /var into a single subvolume. An update of this was possible, but only offline (i.e., via a rescue system).
2- a disk too small for their use - 40GB should be fine for many users, but that is just a default. After all anyone storing anything in /var, such as logs, is going to be 'robbing' space otherwise useful for snapshots </quote>
WTF? Those are the YAST defaults.
ACK on that one, even more as in the old state (with the many /var subvolumes) changing the root size was non-trivial. But AFAIK this is fixed now, too.
Is that the problem? If someone actually uses /var, then the defaults are insufficient for btrfs and that leads to / running out of space? Should YAST pick up on the "old btrfs layout" a change appropriately to avoid the slight annoyances?
Not for btrfs. If someone creates tons of logfiles (running mail- and webservers) or uses it for development the default settings are on the low side for any system that doesn't just use the whole partition for everything...
It seems like there should be a preliminary question (or two), or at least an information box on the YAST partitioning page that could provide guidance here. Especially if it will help avoid problems.
You're talking about the past, is it? As I understood Leap 15 is already in a much improved state (single /var, quota enabled to monitor usage and auto-clean snapshots). Normal users *should* be on the safe side by now.
/var holds the mail stores, fax stores, mysql tables, cups-pdf and a combination of other system and user files that can vary wildly in size. It would be useful to at least inform, if not have a separate question before the partitioning page in YAST to clarify
"Do you have storage requirements for a large number of logs, mail users, a fax server or a large database that will require additional storage?"
YAST adds a separate /var partition
In general one might indeed consider offering this as an option, a radio button '/var on separate partition' and some explanations in the help.
No doubt progress is being made. We have gone from weekly "Root is full" posts to monthly or less -- to that's progress, but if the new user which opensuse has been geared to for the past decade is still have problems with the YAST default partitioning and filesystem selection -- then there is still more to do.
I think you'll have to wait a bit more. How many of such posts are from Leap 15 users? With the fixes you won't help any Leap 42.x or old TW user. Some care likely needs to be taken of upgraded systems, as that never(?) touches/changes the partitioning layout.... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org