Adrian von Bidder wrote: > Hi, > > On Tuesday 12 January 2010 08.08:26 Piavlo wrote: > >> Maintaining snapshot hierarchy by external application is not reliable >> and error prone >> compared to maintaining it withing the btrfs itself, >> probably by adding the parent treeid field for every shapshot/subvolume. >> > > What should, in your opinion, happen if the parent snapshot is deleted? > Orphan? Re-parent to parent of parent? Re-parent to parent of parent. And if there is no grandparent then point to itself (like with root directory). This hierarchy should be tracked/modifed within same subvolume only - so each subvolume has it's own snapshots hierarchy. This would allow, for example, easy rollback of most recent subvolume state to previous states (probably with btrfsctl) without maintaining snapshots hierarchy state in userspace applications. Thanks Alex > I guess depending on application, > there may be more than one "right" solution. > > cheers > -- vbi > > -- 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
