On 2016-11-02 07:25, Ahmed Badr wrote:
On Wed, Nov 2, 2016 at 2:19 AM, Hans van Kranenburg
<hans.van.kranenburg@xxxxxxxxxx> wrote:
While all of the snapshots with a matching parent_uuid are snapshots of
the same thing in linear time for btrfs, the tools may have their own
added administration on top (like snapshot names, or directories they're
placed in), which prevents them from being able to do something with the
other ones. This is not the fault of btrfs, it's because those tools
probably are designed to ignore anything they didn't cause to happen
themselves.
I understand now. Both apps seems to behave well and do not mess with
each others snapshots so I'm tempted to use both but I think I better
stick to only one as I might get confused with so many snapshots and
rollback to the wrong one.
What I would suggest doing in this case is to split out /home to a
separate filesystem, use snapper for that, and use apt-btrfs-snapshot
for everything else (except possibly stuff which gets served externally
by the system, such as /var/www). That way you get the benefits of
snapper for the files where that type of snapshotting matters, and
apt-btrfs-snapshot for where that actually matters, and you have no
chance of them stepping on each others toes.
Also, make sure to check the settings for snapper, the defaults are
pathologically bad for most end-users and will quite often put you in a
bad situation eventually with the filesystem. What actually works is up
to your use case, but you almost certainly don't need snapshots more
frequently than every few minutes.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
