Anton Aylward wrote:
On 03/14/2016 09:42 AM, Carlos E. R. wrote:
On 2016-03-14 14:22, Anton Aylward wrote:
I think Ruben's complaint is that left to itself the installer created a lot of subvolumes and you really can't tell the space that they are each using from running a 'df'. A reason to dislike BtrFS? Well it was designed that way, which may be wrong. Which is why I created 'real' partitions (see above). The installer will honour them.
There are strong reasons to create all those "spaces" when using btrfs. One, is that when reverting an update by using that feature, you must not revert the logs and other information. Then for directories used for databases you should not use COW. Ie, it is for properly adjusting the settings on each directory, even if they are all in the same partition.
So, yes, leave those spaces alone ;-)
I have come to think that this is a weak argument.
I recall the ability to roll-back updates on mainframes-class machines and even some versions of AIX where IBM customers wanted the same capability as they had on the mainframes from IBM.
Yes, on z/OS (aka MVS), PTF's, APAR's and SYSMOD's are easily "rolled" on and off using SMP/E. Well, twenty years ago at least.
But user-space is different. Its all very well to take daily (perhaps incremental) backups of user space under /home (perhaps to the cloud) but the reality is that period is too great for the majority of mistakes users make.
Undo, Ctrl-Z and the daily backup has actually served me quite well for the last 30 years :-) -- Per Jessen, Zürich (5.1°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org