On Tue, Dec 17, 2013 at 10:40:41AM -0500, Michael Welsh Duggan wrote: > David Sterba <dsterba@xxxxxxx> writes: > > > On Tue, Dec 17, 2013 at 05:13:49PM +0800, Wang Shilong wrote: > >> If we change our default subvolume, btrfs receive will fail to find > >> subvolume. To fix this problem, i have two ideas. > >> > >> 1.make btrfs snapshot ioctl support passing source subvolume's objectid > > > >> 2.when we want to using interval subvolume path, we mount it other place > >> that use subvolume 5 as its default subvolume. > > > > 3. Tell the user to mount the toplevel subvol by himself and run receive > > again > > Ugh. I hope that would be considered a short-term hack waiting for a > better solution, perhaps requiring a kernel upgrade. From a user's > perspective there is no reason this should be necessary, and requiring > this would be extraordinarily surprising. "Why is btrfs unable to find > my snapshot? It's right there!" Moreover, this used to work just fine > in previous versions of btrfs-progs. It is a short-term fix, one that we can apply immediatelly without breaking things. A long-term fix is #1, but this would need more work and testing. david -- 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
