On Jul 23, 2013, Jerome Haltom was...@cogito.cx wrote:
Why not just create the new dev_id on the destination snapshot of any
directory? That way the snapshot can share inodes with is source.
Agreed. Nothing stops us from implementing snapshotting of any
directory whatsoever: all it takes is
May I ask why the decision to implement snapshotting through
subvolumes? I've been very curious about why the design wasn't to
simply allow snapshotting of any directory or file.
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to
Now... since the snapshot's FS tree is a direct duplicate of the
original FS tree (actually, it's the same tree, but they look like
different things to the outside world), they share everything --
including things like inode numbers. This is OK within a subvolume,
because we have the
On Tue, Jul 23, 2013 at 07:47:41PM +0200, Gabriel de Perthuis wrote:
Now... since the snapshot's FS tree is a direct duplicate of the
original FS tree (actually, it's the same tree, but they look like
different things to the outside world), they share everything --
including things like
Le mar. 23 juil. 2013 21:30:13 CEST, Hugo Mills a écrit :
On Tue, Jul 23, 2013 at 07:47:41PM +0200, Gabriel de Perthuis wrote:
Now... since the snapshot's FS tree is a direct duplicate of the
original FS tree (actually, it's the same tree, but they look like
different things to the outside
Why not just create the new dev_id on the destination snapshot of any
directory? That way the snapshot can share inodes with is source.
On Tue, Jul 23, 2013 at 2:30 PM, Hugo Mills h...@carfax.org.uk wrote:
On Tue, Jul 23, 2013 at 07:47:41PM +0200, Gabriel de Perthuis wrote:
Now... since the
On Jul 23, 2013, at 1:43 PM, Jerome Haltom was...@cogito.cx wrote:
Why not just create the new dev_id on the destination snapshot of any
directory?
Right now, snapshots of subvolumes do not contain the contents of contained
subvolumes. Hmmm, that sounds horrid.
Subvolume A
File 1
Yeah. I was merely curious about the architecture limits that drove
the design this way, to begin with. Mostly because it seems odd. It
seems like the most obvious and most natural thing from the user's
perspective to do would just be able to reflink directories. Like
every decent source control
On Tue, Jul 23, 2013 at 06:39:57PM -0500, Jerome Haltom wrote:
Yeah. I was merely curious about the architecture limits that drove
the design this way, to begin with. Mostly because it seems odd. It
seems like the most obvious and most natural thing from the user's
perspective to do would just
On Jul 23, 2013, at 7:27 PM, Josef Bacik jba...@fusionio.com wrote:
Subvolumes are described as directories simply to make it easier to
understand.
Directories do not change the heirarchy within the file system itself, they
are
simply items in the btree like anything else, they are not
10 matches
Mail list logo
