On Thu, Jul 16, 2015 at 01:12:03PM +1000, Paul Harvey wrote: > On 16 July 2015 at 11:35, Chris Murphy <li...@colorremedies.com> wrote: > > On Wed, Jul 15, 2015 at 6:11 PM, Johannes Ernst > > <johannes.er...@gmail.com> wrote: > > > >> Cleaning this all up is a bit of pain, and > >> btrfs subvolume delete -r dir > >> would solve it nicely. > > [snip] > > > How is all of this backed up properly? How is it restored properly? I > > think recursive snapshotting and subvolume deletion is not a good > > idea. I think it's a complicated and inelegant work around for > > improper subvolume organization. > > I for one would love to see authoritative documentation on "proper" > subvolume organization. I was completely lost when writing snazzer and > have so far received very little guidance or even offers of opinions > on this ML.
Advice on this point has been on the btrfs wiki for several years, at: https://btrfs.wiki.kernel.org/index.php/SysadminGuide#Managing_snapshots Hugo. > I've had to create my own logic in my scripts that automatically walk > all subvolumes on all filesystems for the simple reason that > explicitly enumerating it all for dozens of servers becomes a > significant administration burden. > > I have different retention needs for /var (particularly /var/cache) > than I do for /home, for example, so carving up my snapshots so that I > can easily drop them from those parts of my filesystems which have a > high churn rate (= more unique extents, occupying a lot of disk) and > yet aren't as important (I need to retain fewer of them) is very > useful. -- Hugo Mills | Hail and greetings. We are a flat-pack invasion hugo@... carfax.org.uk | force from Planet Ikea. We come in pieces. http://carfax.org.uk/ | PGP: E2AB1DE4 |
signature.asc
Description: Digital signature
