On 17 January 2014 17:52, James Hogarth wrote:
>
>
> Filed https://bugzilla.redhat.com/show_bug.cgi?id=1054903 to get the
> anaconda point of view and a decision on default layout for a BTRFS based
> Fedora system.
>
>
So I moved my home from being alongside root in subvolid=0 to being under
root
On 17 January 2014 14:10, James Hogarth wrote:
>
>
> Thanks that commit does indeed match my behaviour ... even if it seems a
> bit messed up all things considered ...
>
> I might use a Fedora Live instance and remove the /home mount point whilst
> maintaining as a subvolume within root ...
>
> I
On 17 January 2014 13:38, Chris Murphy wrote:
>
> On Jan 17, 2014, at 6:06 AM, James Hogarth
> wrote:
>
>
> So far as I understand it when in the same pool cross-subvolume COW should
> be valid (as shown in /data on the server) - even if technically under
> separate mounts.
>
>
> I haven't yet f
On Jan 17, 2014, at 6:06 AM, James Hogarth wrote:
>
> So far as I understand it when in the same pool cross-subvolume COW should be
> valid (as shown in /data on the server) - even if technically under separate
> mounts.
I haven't yet found anything newer than this:
http://git.kernel.org/cgi
Hi all,
I've encountered something that seems a little weird and wondering if
anyone has any ideas...
My home server has an ext4 root with a btrfs pool mounted at /data (with a
number of subvolumes in there).
Within /data I am able to do cp --reflink=always between
subvolumes and COW works as
