From: Clemens Eisserer <linuxhippy@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Can btrfs cope with a high number of snapshpts (continuous snapshotting)?
Date: Fri, 10 May 2013 10:30:29 +0200 [thread overview]
Message-ID: <CAFvQSYQFPtoAXncHopDg4W=Br5Cy3EjR+EKrhUZP0FFg0Fh09A@mail.gmail.com> (raw)
Hi,
I am looking for a file-system which is able to provide continuous
snapshotting like some log-structured file-systems do.
The btrfs snapshot-mechanism seems to be what I am looking for, in
combination with a daemon monitoring the free space it should be
possible to create a snapshot every 15min and delete snapshots as the
free space is below some threshold.
Is btrfs suitable for such a high number of snapshots, or will it have
negative implications (like huge metadata, ...)?
Thank you in advance, Clemens
reply other threads:[~2013-05-10 8:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAFvQSYQFPtoAXncHopDg4W=Br5Cy3EjR+EKrhUZP0FFg0Fh09A@mail.gmail.com' \
--to=linuxhippy@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).