public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: TARUISI Hiroaki <taruishi.hiroak@jp.fujitsu.com>
To: andrey.v.kuzmin@gmail.com
Cc: mniederle@gmx.at, linux-btrfs@vger.kernel.org
Subject: Re: snapshots of directories
Date: Thu, 14 Jan 2010 09:40:52 +0900	[thread overview]
Message-ID: <4B4E6814.1020405@jp.fujitsu.com> (raw)
In-Reply-To: <2a31deca1001131104s1181bc89nbcc719d0b9e4b0ab@mail.gmail.com>

Yes. I mean that.
In detail, 'non subvolume directory' may be more precise
than 'arbitrary directory'.

Thanks for your description.

Regards,
taruisi

(2010/01/14 4:04), Andrey Kuzmin wrote:
> Did I get you right in that btrfs does not support snapshots of an
> arbitrary directory?
> 
> Regards,
> Andrey
> 
> 
> 
> 
> On Tue, Jan 12, 2010 at 5:19 AM, TARUISI Hiroaki
> <taruishi.hiroak@jp.fujitsu.com> wrote:
>> In btrfs, snapshot is a clone of subvolume, not arbitrary
>> directory.
>> You specified '/root' directory and it is not subvolume,
>> snapshot is created for parent subvolume, root of filesystem.
>>
>> Regards,
>> taruisi
>>
>> (2010/01/12 11:12), Michael Niederle wrote:
>>> I try to take a snapshot of a single directory, e.g. root:
>>>
>>>> btrfsctl -s root.2010-01-12 /root
>>> operation complete
>>> Btrfs v0.19-4-gab8fb4c-dirty
>>>
>>> Then I take look what's inside the newly created snapshot:
>>>
>>>> ls -l /root.2010-01-12/
>>> total 0
>>> drwxr-xr-x 1 root root 1192 2010-01-03 20:32:12 bin
>>> drwxr-xr-x 1 root root   76 2009-06-25  0:40:35 boot
>>> drwxr-xr-x 1 root root 1756 2010-01-12  2:33:07 cmds
>>> drwxr-xr-x 1 root root    0 2010-01-06 12:21:46 data
>>> drwxr-xr-x 1 root root 4356 2010-01-12  2:07:00 dev
>>> drwxr-xr-x 1 root root   42 2010-01-04 12:29:45 downloads
>>> drwxr-xr-x 1 root root 4528 2010-01-12  2:12:12 etc
>>> drwxr-xr-x 1 root root   52 2010-01-11 12:57:47 home
>>> drwxr-xr-x 1 root root    0 2007-11-10  4:44:07 initrd
>>> drwxr-xr-x 1 root root 4490 2010-01-05 20:15:53 lib
>>> drwxr-xr-x 1 root root  124 2008-04-27 14:53:39 mnt
>>> drwxr-xr-x 1 root root   62 2008-01-08  0:21:58 net
>>> drwxr-xr-x 1 root root    0 2008-04-09  3:19:16 objects
>>> drwxr-xr-x 1 root root  316 2009-12-28 23:23:13 opt
>>> dr-xr-xr-x 1 root root    0 2007-11-10  3:35:28 proc
>>> drwxr-xr-x 1 root root 7676 2010-01-11  0:35:41 root
>>> drwxr-xr-x 1 root root    0 2010-01-12  1:56:17 save
>>> drwxr-xr-x 1 root root    0 2010-01-12  1:55:58 save2
>>> drwxr-xr-x 1 root root 3804 2010-01-06  2:36:08 sbin
>>> drwxr-xr-x 1 root root    0 2007-11-10  3:35:28 sys
>>> drwxr-xr-x 1 root root  358 2010-01-11 18:44:29 tmp
>>> drwxr-xr-x 1 root root  176 2009-12-29 17:08:37 usr
>>> drwxr-xr-x 1 root root   72 2010-01-05 20:03:00 var
>>>
>>> It seems that always a snapshot of the root is taken instead one of the
>>> specified directory? Is this by design?
>>>
>>> Snapshotting the root works fine, but if you take several snapshots it's a bit
>>> "recursive", because every new snapshot contains all previous snapshots.
>>>
>>> Greetings, Michael
>>> --
>>> 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
>>
>> --
>> 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
>>


-- 
taruisi


      reply	other threads:[~2010-01-14  0:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-12  2:12 snapshots of directories Michael Niederle
2010-01-12  2:19 ` TARUISI Hiroaki
2010-01-12  5:44   ` Adrian von Bidder
2010-01-13 19:04   ` Andrey Kuzmin
2010-01-14  0:40     ` TARUISI Hiroaki [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=4B4E6814.1020405@jp.fujitsu.com \
    --to=taruishi.hiroak@jp.fujitsu.com \
    --cc=andrey.v.kuzmin@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=mniederle@gmx.at \
    /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