-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 05/05/15 15:31, Anton Aylward wrote:
On 05/05/2015 10:10 AM, Carlos E. R. wrote:
On 2015-05-05 15:47, Malcolm wrote:
On Tue 05 May 2015 02:50:32 PM CDT, Carlos E. R. wrote:
Maybe, but snapper is only active when "/" is btrfs.
Hi But can be used with others... From http://snapper.io/overview.html
- Works with btrfs, ext4 and thin-provisioned LVM volumes
Ah, yes, true. I should have expressed myself better. Something like openSUSE enables on installation snapper only when using btrfs.
yes, the configs file reads:
# subvolume to snapshot SUBVOLUME="/"
# filesystem type FSTYPE="btrfs"
But that FSTYPE could be something else ...
So we wold have this happeining with ext4! The issue isn't BtrFS in that case, its snapper.
We shouldn't be blaming BtrFS specifically. We may be right in blaming the people who set up this default config, enabling just about everything!
Which is what I just said. - -- Bob Williams System: Linux 3.16.7-7-desktop Distro: openSUSE 13.2 (x86_64) with KDE Development Platform: 4.14.3 Uptime: 06:00am up 7:55, 3 users, load average: 0.16, 0.05, 0.06 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlVI2tcACgkQ0Sr7eZJrmU4O6ACghBzqyp2pokqBdDI3AAxKGqJC 8SoAn089h/6Lc90Ax2sLs2NX472Y21cq =zPbS -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org