Package: snapper Version: 0.1.8-2 Severity: normal Tags: upstream Dear Maintainer,
this is probably a problem for upstream, but I can't find their bug tracker. So here it goes: Snapper stores the snapshots it makes of a subvolume in a subdirectory ..snapshots in that same subvolume. E.g., if I have a configuration home for /home, its snapshots are stored in /home/.snapshots. As a result, programs that traverse the filesystem inadvertantly walk into the snapshots. The simplest case is an invocation of find somewhere above a "snappered" subvolume. Locate/updatedb index each individual snapshot. An NFS export of such a subvolume exposes its snapshots. Presumably, the convention of putting snapshots in a .snapshots subdirectory makes it easier to apply snapper to an existing filesystem. Unfortunately, it breaks other things. Solution: Change the filesystem layout so that snapshots are not stored in (permanently) mounted subvolumes. Compare the layout Ubuntu uses with btrfs: https://help.ubuntu.com/community/btrfs#Ubuntu-specific_subvolume_layout_in_11.04_and_later I suggest snapper use a similar (same?) layout. Michael -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (990, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.12-1-amd64 (SMP w/8 CPU cores) Locale: LANG=POSIX, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages snapper depends on: ii btrfs-tools 3.12-1 ii libboost-system1.54.0 1.54.0-4+b1 ii libboost-thread1.54.0 1.54.0-4+b1 ii libc6 2.18-1 ii libdbus-1-3 1.8.0-1 ii libgcc1 1:4.8.2-16 ii libsnapper2 0.1.8-2 ii libstdc++6 4.8.2-16 ii libxml2 2.9.1+dfsg1-3 ii zlib1g 1:1.2.8.dfsg-1 snapper recommends no packages. snapper suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
