From: Martin <m_btrfs@ml1.co.uk>
To: linux-btrfs@vger.kernel.org
Subject: How many subvols/snapshots are possible? (limits?)
Date: Thu, 09 May 2013 11:10:56 +0100 [thread overview]
Message-ID: <kmfsnb$bu1$1@ger.gmane.org> (raw)
Dear Devs,
This is more a use case question of what is a good idea to do...
Can btrfs support snapshots of the filesystem at very regular intervals,
say minute by minute or even second by second?
Or are there limits that will be hit with metadata overheads or
links/reference limits or CPU overheads if 'too many' snapshots/subvols
are made?
If snapshots were to be taken once a minute and retained, what breaks first?
What are 'reasonable' (maximum) numbers for frequency and number of held
versions?
Thanks,
Martin
next reply other threads:[~2013-05-09 10:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-09 10:10 Martin [this message]
2013-05-09 11:05 ` How many subvols/snapshots are possible? (limits?) Harald Glatt
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='kmfsnb$bu1$1@ger.gmane.org' \
--to=m_btrfs@ml1.co.uk \
--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.