From: Goffredo Baroncelli <kreijack@libero.it>
To: Phillip Susi <psusi@cfl.rr.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Snapshot rollback
Date: Sun, 23 Oct 2011 22:35:20 +0200 [thread overview]
Message-ID: <1420234.7VTvYPTVqo@venice> (raw)
In-Reply-To: <4EA46E3A.9090307@cfl.rr.com>
On Sunday, 23 October, 2011 15:42:50 you wrote:
> there no way to move or hard link subvolumes to somewhere other
> than their original location?
You can use the 'mv' command.
[__active is the subvolume which I use as root]
ghigo@venice:/tmp$ btrfs sub crea a
Create subvolume './a'
ghigo@venice:/tmp$ btrfs sub crea c
Create subvolume './c'
ghigo@venice:/tmp$ btrfs sub crea a/b
Create subvolume 'a/b'
ghigo@venice:/tmp$ sudo btrfs sub list /var/btrfs/
ID 258 top level 5 path __active
ID 259 top level 5 path __active/tmp/a
ID 260 top level 5 path __active/tmp/c
ID 261 top level 5 path __active/tmp/a/b
ghigo@venice:/tmp$ mv a/b c
ghigo@venice:/tmp$ sudo btrfs sub list /var/btrfs/
ID 258 top level 5 path __active
ID 259 top level 5 path __active/tmp/a
ID 260 top level 5 path __active/tmp/c
ID 261 top level 5 path __active/tmp/c/b
--
gpg key@ keyserver.linux.it: Goffredo Baroncelli (ghigo) <kreijack@inwind.it>
Key fingerprint = 4769 7E51 5293 D36C 814E C054 BF04 F161 3DC5 0512
next prev parent reply other threads:[~2011-10-23 20:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-23 19:42 Snapshot rollback Phillip Susi
2011-10-23 20:35 ` Goffredo Baroncelli [this message]
2011-10-24 5:45 ` dima
2011-10-24 5:58 ` Fajar A. Nugraha
2011-10-24 8:24 ` dima
2011-10-24 12:11 ` Fajar A. Nugraha
2011-10-25 2:00 ` dima
2011-10-25 8:01 ` Fajar A. Nugraha
2011-10-25 8:54 ` dima
2011-10-25 9:01 ` Fajar A. Nugraha
2011-10-25 0:45 ` Phillip Susi
2011-10-25 2:04 ` Arand Nash
2011-10-26 1:30 ` Phillip Susi
-- strict thread matches above, loose matches on Subject: below --
2019-07-05 10:38 snapshot rollback Ulli Horlacher
2019-07-05 11:06 ` Ulli Horlacher
2019-07-05 11:47 ` Remi Gauvin
2019-07-05 13:03 ` Graham Cobb
2019-07-05 21:18 ` Chris Murphy
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=1420234.7VTvYPTVqo@venice \
--to=kreijack@libero.it \
--cc=linux-btrfs@vger.kernel.org \
--cc=psusi@cfl.rr.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.