public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian von Bidder <avbidder@fortytwo.ch>
To: linux-btrfs@vger.kernel.org
Subject: Re: snapshot/subvolume removal
Date: Wed, 6 Jan 2010 07:54:12 +0100	[thread overview]
Message-ID: <201001060754.18256@fortytwo.ch> (raw)
In-Reply-To: <4B43D9AB.1090606@jp.fujitsu.com>

[-- Attachment #1: Type: Text/Plain, Size: 941 bytes --]

On Wednesday 06 January 2010 01.30:35 TARUISI Hiroaki wrote:
> 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.
> 

This was a bit confusing to me at first, too.  (But obviously '-s' needs the 
input which volume to take the snapshot from.)

Would it be a good idea to make btrfsctl -s fail if the last argument is not 
the root of a subvolume?  That way, the directory given to "btrfsctl -s" 
would always match what ends up in a snapshot.  (It is a bit strange for 
people who are not familiar with btrfs to do "btrfsctl -s snap 
some/directory/somewhere" and then realize that the snapshot is created from 
"some" and not from "somewhere" because "some" is the subvolume root.)

cheers
-- vbi

-- 
Pushing 40 is exercise enough.

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 389 bytes --]

  reply	other threads:[~2010-01-06  6:54 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 [this message]
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=201001060754.18256@fortytwo.ch \
    --to=avbidder@fortytwo.ch \
    --cc=linux-btrfs@vger.kernel.org \
    /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