On 26/02/17 07:18 PM, Carlos E. R. wrote:
The rollback feature works, and it is a fact that it needs control of the root filesystem, with many directories.
stop and think for a moment what you mean by the term "root filesysrem". My root file systems excludes, has always excluded, /home and /tmp. To simplify upgrades, and to preserve data across upgrades, as well as principles of good functional compartmentalization, never mind efficiency and management of such things as backups, I also have separated out things that are clearly data, the FS for the web site(s), the FS for the SQL database. The SQL database? Well depending... Sometimes that's implemented as a separate file for each table, separate file for each index. on other implementations its implemented as a single big file that is managed as a whole by the DBMS. In the latter case, snapshotting the while file for a single change in a single table is going to be expensive! All in all I look to the dynamics and the value of using snapper vs conventional daily backup vs thin provisioning. I consider the operational processes involved. For example, I can upgrade 13.2 to LEAP by creating a new LVM logical volume for the RootFS, keeping, for example, my old /home and /srv (as well as /tmp that I just reformat) around[1]. If LEAP fails I just go back to using /dev/vgmain/vROOT132 rather than /dev/vgmain//vROOR421 I keep telling people "Context is Everything". There are no absolutes. [1] Heck, there is a lot of free LVM space in this multi-terabyte drive! -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org