All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Pottage <david@electric-spoon.com>
To: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: snapshot limit?
Date: Tue, 17 Aug 2010 22:13:41 +0100	[thread overview]
Message-ID: <4C6AFB85.9020207@electric-spoon.com> (raw)
In-Reply-To: <4C6AD78B.8070503@noir.com>

 On 17/08/10 19:40, K. Richard Pixley wrote:
> On 8/17/10 11:05 , Dhiru Kholia wrote:
>> On Tue, Aug 17, 2010 at 10:41 AM, K. Richard Pixley <rich@noir.com
>> <mailto:rich@noir.com>> wrote:
>>  >  Is there a limit to the number of snapshots that can exist on a file
>> system
>>  > concurrently?
>>
>> According to https://help.ubuntu.com/community/btrfs "You can create
>> as many subvolumes as you want, as long as you have storage capacity."
>>
>> -- 
>> Cheers,
>> Dhiru
>>
>
> Yes.  But if there's a limit to the number of paths that can point to
> a single file, then that's not strictly true.  Rather, there's a limit
> based on the number of snapshots pointing to the same file.

Would that limit also apply to de-duplicated copies of a file ?

Suppose I have tree under a btrfs file-system with lots of identical
files. (eg zero length lock files), and I run a de-duplication script on
it, to turn all those files into one, and then make a series of snapshots.

100 identical files multiplied by 100 snapshots (eg. daily for a few
months), comes to a rather large number of links pointing to the same file.

-- 
David Pottage


      reply	other threads:[~2010-08-17 21:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-17 17:41 snapshot limit? K. Richard Pixley
     [not found] ` <AANLkTin1kV1ebL-qOvOOv2e=DZ5qvyWYEEreg-+vqDdP@mail.gmail.com>
2010-08-17 18:40   ` K. Richard Pixley
2010-08-17 21:13     ` David Pottage [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=4C6AFB85.9020207@electric-spoon.com \
    --to=david@electric-spoon.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 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.