-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On Mon, 2017-01-23 at 12:27 -0800, L A Walsh wrote:
If you use btrfs with snasphots and rollback, it is always on the root volume.
---- "Best practices" wouldn't apply to someone using brtfs considering the ongoing problems people post to open-suse. I can't see it being ready for a production system or one that one wants to "keep up" and have 24x7 uptime.
I just want to clarify... there's a huge gap between the issues we see with btrfs and Tumblweeed and the issues that come up with btrfs on SLES. Tumbleweed, with it's _massive_ package churn, highlights a lot of issues with btrfs that no SLES customer would ever hit. So, the differentiation on what makes a "24x7 uptime" server isn't the file system, but the whole OS: and here Tumbleweed is a clearly inferior choice to SLES. - -- James Mason Technical Architect, Public Cloud openSUSE Member SUSE jmason@suse.com -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEg/RjZ+RraZBnLRN4GzlRiGxEkCMFAliGaqsACgkQGzlRiGxE kCPklwf/fqhVes5o4cbwKfZQi8htI8c5C8/aHRpFZcwJsqjhwJRk6W5/UoX+9UJx JmNhgAp9/KH01javbldrmyiBvrrqBTYDN2US5Khay4Bs+Xix1Qw0o7tjdBvR6nL4 4wEmFHy9pCpyZqy7i6EN6MbokTUTyiBtCIT2G+HsdjSu4h60sd0bUpu2NG5tJ1I6 REmhgXhtBZB+ZXnUHKPvlxjbM6RusOm1gqRk5FJeOL/nv83XphfAJRirAfVylDgG Zx+ztTUDsGBGAysMfRRZOU+wBOIBdYD4yWQjh8wFld3Qwd5UhaohbHh7QheZAaDp 3l+vOt+3ujbZ+dX4Twl85ZCZbkATHw== =//Jc -----END PGP SIGNATURE----- N�����r��y隊Z)z{.���r�+�맲��r��z�^�ˬz��N�(�֜��^� ޭ隊Z)z{.���r�+��0�����Ǩ�