On Thu, 22 Dec 2011 10:57:10 PM Gareth Pye wrote:
> Chris, I recommend reading the previously linked thread.
Mea culpa, I blame reading email out of order after getting out of
hospital yesterday. :-(
We now return you to your regularly scheduled mailing list..
--
Chris Samuel : http://www.
Chris Samuel wrote (ao):
> On Thu, 22 Dec 2011 07:12:13 PM Roman Kapusta wrote:
> > I'm using btrfs for about two years and this is the key feature I'm
> > missing all the time. Why is it not part of mainline btrfs already?
>
> Because nobody has written the code to do it yet?
>
> I'm sure the de
Chris, I recommend reading the previously linked thread. The supplied
(and reportedly working) patch was nacked because it violates some
principles or another of file systems. (although from my limited
understanding it only does it in the same way that btrfs snapshots do
in the first place)
On Thu
On Thu, 22 Dec 2011 07:12:13 PM Roman Kapusta wrote:
> I'm using btrfs for about two years and this is the key feature I'm
> missing all the time. Why is it not part of mainline btrfs already?
Because nobody has written the code to do it yet?
I'm sure the developers would welcome patches for thi
Did you get any success with the patch?
Reading the conversation, people seemed to agree that this feature
should be included, anyway, snapshot already share data, why not be
able to copy them?
Other link with title for mailing list reference.
[PATCH 2/2] btrfs: allow cross-subvolume BTRFS_IOC_CLO
You would need to apply this patch to your kernel:
http://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg09096.html
Is there any chance this patch gets in linux-next ?
I use this feature all the time and it never broke on me.
On Tue, Dec 20, 2011 at 10:07 AM, Dave wrote:
>
> -BEGIN PGP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
So I've got a daily snapshot of my /home subvolume. Due to a fat finger, I've
damaged a rather large file so I'd like to pull if from one of these snapshot
backups. I don't want to simply copy the file since it's many gigs and cp
- --reflink=always