From: TARUISI Hiroaki <taruishi.hiroak@jp.fujitsu.com>
To: piavka@cs.bgu.ac.il
Cc: linux-btrfs@vger.kernel.org
Subject: Re: snapshot/subvolume removal
Date: Tue, 12 Jan 2010 09:48:18 +0900 [thread overview]
Message-ID: <4B4BC6D2.6030906@jp.fujitsu.com> (raw)
In-Reply-To: <4B48FCCC.9050004@cs.bgu.ac.il>
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
next prev parent reply other threads:[~2010-01-12 0:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-05 21:18 snapshot/subvolume removal Piavlo
2010-01-06 0:30 ` TARUISI Hiroaki
2010-01-06 6:54 ` Adrian von Bidder
2010-01-06 8:33 ` Piavlo
2010-01-08 8:28 ` TARUISI Hiroaki
2010-01-09 22:01 ` Piavlo
2010-01-12 0:48 ` TARUISI Hiroaki [this message]
2010-01-12 7:08 ` Piavlo
2010-01-12 8:04 ` TARUISI Hiroaki
2010-01-12 9:12 ` Adrian von Bidder
2010-01-12 11:03 ` Piavlo
2010-01-10 20:18 ` Chris Mason
2010-01-12 1:12 ` TARUISI Hiroaki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B4BC6D2.6030906@jp.fujitsu.com \
--to=taruishi.hiroak@jp.fujitsu.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=piavka@cs.bgu.ac.il \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox