Dne pondělí 17. října 2016 21:49:19 CEST, Michael Hamilton napsal(a):
I was looking to make an exact copy of a tumbleweed root btrfs filesystem on removable media. One aspect that makes this more fiddly is the number of subvolumes that are part of the root filesystem, including /opt and many sub-directories of /var.
Really? E.g. /var/lib/mariadb is better to handle with tools like automysqlbackup anyway. I see it OK.
Is there any technical document describing the reasons behind having so many subvolumes? Someone else was asking the same question at stackexchange (with no real answers) :
Is this enough? https://www.suse.com/documentation/sles-12/stor_admin/data/ sec_filesystems_major.html
http://unix.stackexchange.com/questions/285011/why-does-my-tumbleweed-opensu se-fstab-contain-so-many-btrfs-subvol-entries
Is there a recommended way to get a faithful offline bootable backup of a btrfs rootfs?
I don't know if recommended, but dd?
Finally, I'm not determined to use btrfs. I'm moving up from 13.1. I'm evaluating Leap and Tumbleweed. It's a simple desktop, no RAID, one user. Would ext4 be a better choice?
Then I'd keep Btrfs anyway - its possibility of snapshots, i.e. possibility to roll back to previous version from many failures (power outage in the middle of big upgrade etc.) is really great. The subvolumes typically exclude quickly changing temporary, DB, cache, ... directories from snapshots to save space and the disk. -- Vojtěch Zeisek Komunita openSUSE GNU/Linuxu Community of the openSUSE GNU/Linux https://www.opensuse.org/ https://trapa.cz/