Thanks for your comment. I think your request is reasonable but because there's no information about a hierachy of snapshots in filesystem, we cannot know it for now.
In future, these information may be supplied by application programs which manage all snapshots or backups. Regards, taruisi (2010/01/10 07:01), Piavlo wrote: > TARUISI Hiroaki wrote: >> For now, subvolumes and snapshots look like just directories. >> If you want to distinguish them, there's only an unusual way, >> that is, analyzing with btrfs-debug-tree. >> >> I posted patches for listing snapshots/subvolumes two months ago, >> and Josef Bacik posted its bugfix patch. This feature may be >> delivered in sooner or later. >> If you want to try it now, check these URLs. >> http://patchwork.kernel.org/patch/60923/raw/ >> http://patchwork.kernel.org/patch/60920/raw/ >> http://patchwork.kernel.org/patch/67332/raw/ >> > Thanks for pointing me all the needed patched, the btrfsctl -l is > working for me fine. >> Patches and requests are welcome. >> > Currently btrfsctl -l show only which directories are > snapshots/subvolumes, it would be nice if it would also show > a hierarchy of snapshots i.e. from which subvolume/snapshot a specific > snapshot was taken from. > > For example: > > / # cd /.btrfs > /.btrfs # btrfsctl -l /.btrfs > Base path = /.btrfs/ > No. Tree ID Subvolume Relative Path > 1 275 rootfs-old/ > 2 277 rootfs/ > operation complete > Btrfs v0.19-4-gab8fb4c-dirty > /.btrfs # btrfsctl -S subvol0 . > operation complete > Btrfs v0.19-4-gab8fb4c-dirty > /.btrfs # btrfsctl -l /.btrfs/ > Base path = /.btrfs/ > No. Tree ID Subvolume Relative Path > 1 275 rootfs-old/ > 2 277 rootfs/ > 3 279 subvol0/ > operation complete > Btrfs v0.19-4-gab8fb4c-dirty > /.btrfs # btrfsctl -s subvol0-snap subvol0 > operation complete > Btrfs v0.19-4-gab8fb4c-dirty > /.btrfs # btrfsctl -s subvol0/subvol1-snap subvol0 > operation complete > Btrfs v0.19-4-gab8fb4c-dirty > /.btrfs # btrfsctl -s subvol1-snap-snap subvol0/subvol1-snap > operation complete > Btrfs v0.19-4-gab8fb4c-dirty > /.btrfs # btrfsctl -l /.btrfs/ > Base path = /.btrfs/ > No. Tree ID Subvolume Relative Path > 1 275 rootfs-old/ > 2 277 rootfs/ > 3 279 subvol0/ > 4 281 subvol0/subvol1-snap/ > 5 280 subvol0-snap/ > 6 282 subvol1-snap-snap/ > operation complete > Btrfs v0.19-4-gab8fb4c-dirty > / .btrfs # > > It would be nice if it would possible to show the youngest snapshot > ancestor - something like this: > > /.btrfs # btrfsctl -l /.btrfs/ > Base path = /.btrfs/ > No. Tree ID Subvolume Relative Path Snapshot Ancestor > 1 275 rootfs-old/ none > 2 277 rootfs/ > rootfs-old/ > 3 279 subvol0/ none > 4 281 subvol0/subvol1-snap/ subvol0/ > 5 280 subvol0-snap/ subvol0/ > 6 282 subvol1-snap-snap/ > subvol0/subvol1-snap/ > operation complete > Btrfs v0.19-4-gab8fb4c-dirty > /.btrfs # btrfsctl -D subvol1-snap subvol0 > operation complete > Btrfs v0.19-4-gab8fb4c-dirty > /.btrfs # btrfsctl -l . > Base path = /.btrfs/ > No. Tree ID Subvolume Relative Path Snapshot Ancestor > 1 275 rootfs-old/ none > 2 277 rootfs/ > rootfs-old/ > 3 279 subvol0/ none > 4 280 subvol0-snap/ subvol0/ > 5 282 subvol1-snap-snap/ subvol0/ > operation complete > Btrfs v0.19-4-gab8fb4c-dirty > /.btrfs # btrfsctl -D subvol0 . > operation complete > Btrfs v0.19-4-gab8fb4c-dirty > /.btrfs # btrfsctl -l . > Base path = /.btrfs/ > No. Tree ID Subvolume Relative Path Snapshot Origin > 1 275 rootfs-old/ none > 2 277 rootfs/ > rootfs-old/ > 3 280 subvol0-snap/ none > 4 282 subvol1-snap-snap/ none > operation complete > Btrfs v0.19-4-gab8fb4c-dirty > /.btrfs # > > Thanks > Alex -- 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
