On Jan 16, 2014, at 8:38 AM, Neal Becker <ndbeck...@gmail.com> wrote:

> I hope this is an appropriate place to ask user questions.
> 
> I'm trying out snapshot and replication.  I have
> 
> /dev/sda3 on / type btrfs (rw,relatime,ssd,space_cache)
> /dev/sda3 on /home type btrfs (rw,relatime,ssd,space_cache)
> 
> create a subvolume for snapshots:
> 
> #btrfs sub create /.snapshots
> Create subvolume '//.snapshots'
> 
> [root@nbecker1 nbecker]# btrfs subvolume list /
> ID 256 gen 563396 top level 5 path home
> ID 258 gen 563396 top level 5 path root
> ID 372 gen 563396 top level 258 path .snapshots
> 
> [root@nbecker1 nbecker]# btrfs sub snapshot -r /home /.snapshots
> Create a readonly snapshot of '/home' in '/.snapshots/home'
> 
> [root@nbecker1 nbecker]# btrfs subvolume list /
> ID 256 gen 563398 top level 5 path home
> ID 258 gen 563398 top level 5 path root
> ID 372 gen 563398 top level 258 path .snapshots
> ID 373 gen 563398 top level 258 path .snapshots/home
> 
> [root@nbecker1 nbecker]# btrfs send /.snapshots/home > /dev/null
> At subvol /.snapshots/home
> ERROR: open root/.snapshots/home failed. No such file or directory

It's not OK to multipost. You should have crossposted. Or better, pick one 
list, wait some reasonable time for an answer, then post to a different list. 
Otherwise you look impatient and are just wasting people's time reading and 
answering emails they've already read or answered elsewhere. 

Like I said on Fedora Users, this command:
> btrfs sub snapshot -r /home /.snapshots

has created a read-only snapshot of /home, inside 
<TOP_level>/root/.snapshots/home

And this:
> [root@nbecker1 nbecker]# btrfs send /.snapshots/home > /dev/null
> At subvol /.snapshots/home
> ERROR: open root/.snapshots/home failed. No such file or directory

That could be a bug. I'm able to reproduce this on 3.13.0-0.rc8.

Chris Murphy--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to