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: Fri, 08 Jan 2010 17:28:42 +0900 [thread overview]
Message-ID: <4B46ECBA.2030402@jp.fujitsu.com> (raw)
In-Reply-To: <4B444AD5.1060501@cs.bgu.ac.il>
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/
Patches and requests are welcome.
Regards,
taruisi
(2010/01/06 17:33), Piavlo wrote:
> TARUISI Hiroaki wrote:
>> Hi,
>>
>> We can delete snapshot with btrfsctl -D . It's available for
>> your btrfs-progs version.
> -D works great
>
> Also how can I know if some directory is subvolume or snapshot or just a
> normal directory?
> Is there a way to list all the existing snapshots & subvolumes under btrfs?
>
> Thanks
> Alex
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-01-08 8:28 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 [this message]
2010-01-09 22:01 ` Piavlo
2010-01-12 0:48 ` TARUISI Hiroaki
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=4B46ECBA.2030402@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