Re: [systemd-devel] systemd and nested Btrfs subvolumes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, 20.03.15 18:08, Chris Murphy (lists@xxxxxxxxxxxxxxxxx) wrote:

> Sure but now it's missing if you do a rollback, or if you mount any
> different root tree, so immediately special handling is needed.
> 
> If machines is a subvolume at the top level, it can always be mounted
> at /var/lib/machines regardless of which root is used.
> 
> I also think this is more consistent with
> http://0pointer.net/blog/revisiting-how-we-put-together-linux-systems.html
> specifically the section "What We Propose" when it comes to the
> location and naming convention for Btrfs subvolumes.

containers are recursively stackable, hence having toplevel subvolumes
doesn't work, since the containers should be able to have
subcontainers of their own...

Also, it kinda defeats the whole point of btrfs' subvolume concept,
where subvolumes are little more than special directories.

Lennart

-- 
Lennart Poettering, Red Hat
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Filesystem Development]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux