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: Wed, 06 Jan 2010 09:30:35 +0900 [thread overview]
Message-ID: <4B43D9AB.1090606@jp.fujitsu.com> (raw)
In-Reply-To: <4B43AC9B.5030109@cs.bgu.ac.il>
Hi,
We can delete snapshot with btrfsctl -D . It's available for
your btrfs-progs version.
And parameters of btrfsctl -s/S are not coherent at the last
argument.
In creating snapshots, the last argument implies the directory
where subvolume is to be created, but in taking snapshots,
the last argument implies subvolume we take snapshot of, and
snapshots are created under current directory.
So,
> shell> btrfsctl -s rsync-snap rsync
> operation complete
snapshot rsync-snap is created under current directory, and,
> Btrfs v0.19-4-gab8fb4c-dirty
> shell> btrfsctl -S rsync-snap rsync
> operation complete
subvolume rsync-snap is created under rsync directory in current
directory. They are created under different directories.
Regards,
taruisi
(2010/01/06 6:18), Piavlo wrote:
> Hi,
>
> Does btrfs support snapshot or/and subvolume removal ?
> If yes how, since I could not find the commands to do that?
> If not is there any estimation when this feature will be available?
>
> Is there a tool to list the existing subvolumes/snapshots?
>
> It looks like the snapshots can overridden by subvolumes, see below:
>
> shell> btrfsctl -s rsync-snap rsync
> operation complete
> Btrfs v0.19-4-gab8fb4c-dirty
> shell> btrfsctl -S rsync-snap rsync
> operation complete
> Btrfs v0.19-4-gab8fb4c-dirty
> shell> btrfsctl -s rsync-snap rsync
> ioctl:: File exists
> shell>
>
> Is that expected?
> What happens to the snapshot then it is overridden by subvolume?
> It does not seem reasonable that snapshot can be converted into
> subvolume, since newly created subvolume
> holds no data ,while the snapshot is a snapshot of other previously
> existing subvolume and holds data.
> So is snapshots simply destroyed prior to subvolume creation, in the
> above scenario?
>
> 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-06 0:30 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 [this message]
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
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=4B43D9AB.1090606@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