linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Xavier Nicollet <nicollet@jeru.org>
To: Freddie Cash <fjwcash@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs subvolume snapshot syntax too "smart"
Date: Tue, 5 Apr 2011 16:29:58 +0200	[thread overview]
Message-ID: <20110405142958.GK18890@jeru.org> (raw)
In-Reply-To: <BANLkTimbmwM078e-SVcuWPDqjy99_hV+sw@mail.gmail.com>

Le 04 avril 2011 =E0 12:57, Freddie Cash a =E9crit:
> Isn't this a situation where supporting a trailing / would help?
>=20
> For example, with the / at the end, means "put the snapshot into the
> folder".  Thus "btrfs subvolume snapshot /ssd/sub1 /ssd/5/" would
> create a "sub1" snapshot inside the 5/ folder.  Running it a second
> time would error out since /ssd/5/sub1/ already exists.  And if the 5=
/
> folder doesn't exist, it would error out.
>=20
> And without the / at the end, means "name the snapshot".  Thus "btrfs
> subvolume snapshot /ssd/sub1 /ssd/5" would create a snapshot named
> "/ssd/5".  Running the command again would error out due to the
> snapshot already existing.  And if the 5/ folder doesn't exist, it's
> created.  And it errors out if the 5/ folder already exists.
>=20
> Or, something along those lines.  Similar to how other apps work
> with/without a trailing /.

I am not an expert, but I think it is the opposite with rsync.

Cheers,

--=20
Xavier Nicollet
--
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

      reply	other threads:[~2011-04-05 14:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-04 19:09 btrfs subvolume snapshot syntax too "smart" krzf83@gmail.com 
2011-04-04 19:47 ` Goffredo Baroncelli
2011-04-04 19:57   ` Freddie Cash
2011-04-05 14:29     ` Xavier Nicollet [this message]

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=20110405142958.GK18890@jeru.org \
    --to=nicollet@jeru.org \
    --cc=fjwcash@gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).