snap-sync ignores home setting

[NicoHood]

Dont ask me how i triggered this bug, but it ignored the home setting. If i abort the root setting it asks me to backup the home setting. Everything "unnormal" that I did was to try safe the home backup inside a root snapshot and then went one directory upwards. This is obviosly super stupid, but I wanted to test everything.

[alarm@alarmpi snap-sync]$ snapper -c home list
Type   | #  | Pre # | Date                     | User | Cleanup  | Description               | Userdata                                                            
-------+----+-------+--------------------------+------+----------+---------------------------+---------------------------------------------------------------------
single | 0  |       |                          | root |          | current                   |                                                                     
single | 1  |       | Fri Nov 11 19:00:11 2016 | root | timeline | timeline                  |                                                                     
single | 8  |       | Fri Nov 11 19:21:34 2016 | root |          | latest incremental backup | backupdir=////backup, uuid=6c1a3286-34c5-4bbd-a7cc-5762c8dd5ced     
single | 9  |       | Fri Nov 11 19:39:32 2016 | root |          | latest incremental backup | uuid=1e44de19-7755-4219-9884-bc932958ac9e                           
single | 10 |       | Fri Nov 11 19:53:04 2016 | root |          |                           |                                                                     
single | 11 |       | Fri Nov 11 19:54:20 2016 | root |          | latest incremental backup | backupdir=backup/root/13/, uuid=5a9dcbec-12b0-40c3-803a-dc1faac20d33
[alarm@alarmpi snap-sync]$ touch test
[alarm@alarmpi snap-sync]$ sudo snap-sync 
Select a mounted BTRFS device to backup to.
1) 16bfd981-0f5e-4094-b1fb-da0579b560fa (/)
2) 16bfd981-0f5e-4094-b1fb-da0579b560fa (/var/tmp)
3) 16bfd981-0f5e-4094-b1fb-da0579b560fa (/var/log)
4) 16bfd981-0f5e-4094-b1fb-da0579b560fa (/var/abs)
5) 16bfd981-0f5e-4094-b1fb-da0579b560fa (/.snapshots)
6) 16bfd981-0f5e-4094-b1fb-da0579b560fa (/home)
7) 16bfd981-0f5e-4094-b1fb-da0579b560fa (/data)
8) 16bfd981-0f5e-4094-b1fb-da0579b560fa (/srv)
9) 16bfd981-0f5e-4094-b1fb-da0579b560fa (/var/cache/pacman/pkg)
10) 5a9dcbec-12b0-40c3-803a-dc1faac20d33 (/mnt)
0) Exit
Enter a number: 10

You selected the disk with UUID 5a9dcbec-12b0-40c3-803a-dc1faac20d33.
The disk is mounted at /mnt.

Will backup //.snapshots/19/snapshot to /mnt/backup/root/19//snapshot
Continue with backup [Y/n]? n
Aborting backup for this configuration.

Will backup /home/.snapshots/12/snapshot to /mnt/backup/home/12//snapshot
Continue with backup [Y/n]? n
Aborting backup for this configuration.

Done!
[alarm@alarmpi snap-sync]$ sudo snap-sync 
Select a mounted BTRFS device to backup to.
1) 16bfd981-0f5e-4094-b1fb-da0579b560fa (/)
2) 16bfd981-0f5e-4094-b1fb-da0579b560fa (/var/tmp)
3) 16bfd981-0f5e-4094-b1fb-da0579b560fa (/var/log)
4) 16bfd981-0f5e-4094-b1fb-da0579b560fa (/var/abs)
5) 16bfd981-0f5e-4094-b1fb-da0579b560fa (/.snapshots)
6) 16bfd981-0f5e-4094-b1fb-da0579b560fa (/home)
7) 16bfd981-0f5e-4094-b1fb-da0579b560fa (/data)
8) 16bfd981-0f5e-4094-b1fb-da0579b560fa (/srv)
9) 16bfd981-0f5e-4094-b1fb-da0579b560fa (/var/cache/pacman/pkg)
10) 5a9dcbec-12b0-40c3-803a-dc1faac20d33 (/mnt)
0) Exit
Enter a number: 10

You selected the disk with UUID 5a9dcbec-12b0-40c3-803a-dc1faac20d33.
The disk is mounted at /mnt.

Will backup //.snapshots/19/snapshot to /mnt/backup/root/19//snapshot
Continue with backup [Y/n]? y
At subvol //.snapshots/19/snapshot

[wesbarnett]

Would you mind testing this with the master branch and seeing if its still an issue?

[NicoHood]

I read this some minutes ago and my wording is miserable. I will try to test. However this could also be an arm issue, as snapper has some problems on arm. I will try to reproduce, but if not just close it.

[wesbarnett]

Closing. Feel free to reopen if it reoccurs.