All of lore.kernel.org
 help / color / mirror / Atom feed
From: "K. Richard Pixley" <rich@noir.com>
To: Dhiru Kholia <dhiru.kholia@gmail.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: snapshot limit?
Date: Tue, 17 Aug 2010 11:40:11 -0700	[thread overview]
Message-ID: <4C6AD78B.8070503@noir.com> (raw)
In-Reply-To: <AANLkTin1kV1ebL-qOvOOv2e=DZ5qvyWYEEreg-+vqDdP@mail.gmail.com>

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.

Since a snapshot is a copy of an existing file system, the only time a 
snapshot would not have files in common with previous snapshots would be 
in snapshots of empty file systems.  Making snapshots of empty file 
systems begs the question of why one would be bothering with snapshots 
anyway.

Hence, I suspect that in the vast majority of practical cases, there is 
indeed a current limit to the number of snapshots that can be made 
concurrently based on the limit to the number of paths to a single file. 
  I was looking for validation of this theory and perhaps a way to 
detect, avoid, and/or recover from this situation.

I'm experiencing at least one recurring error condition resulting in a 
polluted file system.  I'm using a lot of snapshots in this particular 
application.  So I'm wondering if such a limit exists and/or how to 
determine if I am running into this situation.

Can anyone offer any clarification?

--rich

  parent reply	other threads:[~2010-08-17 18:40 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 [this message]
2010-08-17 21:13     ` David Pottage

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=4C6AD78B.8070503@noir.com \
    --to=rich@noir.com \
    --cc=dhiru.kholia@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 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.