Arch Linux User Repository

@sysfu, the snapper wiki seems to suggest the snapshot dir is in the __active root... you could probably make it work by mounting the real btrfs root somewhere and using a symlink

sysfu, yes it should be as easy as that, if .snapshot/ is in the "real" btrfs root. Give it a try and report back. Thx.

Has anyone attempted to integrate the use of the btrfs Snapper utility with mkinitcpio-btrfs? https://wiki.archlinux.org/index.php/Snapper I recently installed and configured Snapper on my system to make regularly scheduled snapshots. I would like to be able to rollback to these at boot using mkinitcpio-btrfs. Snapper keeps the snapshots in the directory /.snapshots by default. Would it be as simple as editing the /etc/defaults/btrfs_advanced file and changing the line BTRFS_DIR_SNAPSHOT="/__snapshot" to read BTRFS_DIR_SNAPSHOT="/.snapshots" ?

@visit; installed v0.4.1-1 and uncommented the BTRFS_ROLLBACK_KERNEL=false line as instructed, then recreated initrd. Console is nice and clean during boot process now. Thanks for your work on this.

@srf21c, the package is updated. You can now uncomment BTRFS_ROLLBACK_KERNEL=false in /etc/default/btrfs_advanced to disable kernel rollback. Don't forget to recreate your initrd with "mkinitcpio -p linux". Please try it and report any issues. Thanks! P.S.: On the other hand you can try to use BTRFS_KVER_CHECK=true instead. This will reduce the passphrase requests, but still requires the sync of your boot directory between USB-stick and root subvol.

@kodiak, I didn't know about that too. I had the same understanding until I found that in my repro case. Regardless if mkinitcpio-btrfs handles it correct, the purpose of creating subvolumes for curtain FHS directories remains the same - you can handle quotas with it. But for me it makes no sens to neither have recursive snapshots nor dynamic mount of subvolumes from parent snapshots. Maybe its worth to describe this in the btrfs mailinglist and ask for further opinions.

@visit well, I thought not doing snapshots on subvolumes is on purpose, since I do not need any snapshots there?! Maybe some info on the wiki would help newcomers.

@kodiak: Found the issue. There are two of them. 1. You have subvolumes within your root subvolume (home, var, usr), but you did not snapshot them together with the root. Example: # mount -o subvolid=0 /dev/sda2 /mnt # ls -l /mnt/__rollback/usr total 0 Btrfs is not clever enough to mount your existing "sub-subvolumes" to the snapshot created, so you would need to snapshot them too. Like that: # btrfs su sn __active __snapshot/test # rm -r __snapshot/test/{home,var,usr} # btrfs su sn __active/home __snapshot/test/home # btrfs su sn __active/var __snapshot/test/var # btrfs su sn __active/usr __snapshot/test/usr 2. But still this will not work, since the hook is making an additional snapshot of your choosen boot subvolume to __rollback. Currently the hook doesn't recognize "sub-subvolumes" eighter and will NOT snapshot home, var, usr same as you did. So I opened a github bug for #2. https://github.com/xtfxme/mkinitcpio-btrfs/issues/6

@visit: I appreciate your effort on this! that´s the notebook: http://pastebin.com/HQ4VfNcS