From: Thomas Mueller <thomas@chaschperli.ch>
To: ceph-devel@vger.kernel.org
Subject: Re: creation of ./.snap/test creates something in ./subdir/.snap/
Date: Sat, 19 Jun 2010 16:03:28 +0000 (UTC) [thread overview]
Message-ID: <hvipog$r1f$1@dough.gmane.org> (raw)
In-Reply-To: Pine.LNX.4.64.1006190833230.17737@cobra.newdream.net
Am Sat, 19 Jun 2010 08:40:48 -0700 schrieb Sage Weil:
> On Sat, 19 Jun 2010, Thomas Mueller wrote:
>> hi
>>
>> i was looking for a way to list all snapshots*.
>>
>> then i discovered this:
>>
>>
>> mkdir ./.snap/test
>>
>> then i found this:
>> ./.snap/test
>> ./subdir/.snap/_test_1099511630280
>>
>>
>> the subdir/.snap/_test_1099511630280 vanishes if i delete the ./.snap/
>> test.
>
> This is expected, because subdir's contents are contained by the 'test'
> snap, and we want the .snap/ dir to show you all snaps that contain
> copies of the current directory. The name is mangled
> (_$snap_$snap_root_ino) to avoid collisions with the current directory's
> snap namespace. Snaps beginning with _ are disallowed.
>
thanks for the explanation! i've created
http://ceph.newdream.net/wiki/Snapshots
for future reference.
- Thomas
next prev parent reply other threads:[~2010-06-19 16:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-19 7:27 creation of ./.snap/test creates something in ./subdir/.snap/ Thomas Mueller
2010-06-19 15:40 ` Sage Weil
2010-06-19 16:03 ` Thomas Mueller [this message]
2010-06-21 7:30 ` Jerker Nyberg
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='hvipog$r1f$1@dough.gmane.org' \
--to=thomas@chaschperli.ch \
--cc=ceph-devel@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