From: Ryusuke Konishi <ryusuke-sG5X7nlA6pw@public.gmane.org>
To: users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org,
dfuller-ZE272gM1l1AAvxtiuMwx3w@public.gmane.org
Subject: Re: Number of CheckPoints
Date: Thu, 30 Jul 2009 23:38:49 +0900 (JST) [thread overview]
Message-ID: <20090730.233849.87826385.ryusuke@osrg.net> (raw)
In-Reply-To: <4A711C80.1040500-ZE272gM1l1AAvxtiuMwx3w@public.gmane.org>
Hi!
On Wed, 29 Jul 2009 21:07:28 -0700, David Fuller wrote:
> Firstly thanks to Robertas for solving my initial problem with cleanerd
> not running properly on Ubuntu 9.04 . Upgrading the nilfs tools worked
> perfectly.
> I was wondering how many checkpoints are kept and for how many days? I
> see days worth of checkpoints going back about a week.
>
> Regards,
> --David F.
At present, ``protection period'' is the only parameter determining
the assured lifetime of checkpoints.
You can extend or shrink it by changing /etc/nilfs_cleanerd.conf
conffile, and you can store checkpoints up to the capacity of your
drive.
Note that a HUP signal must be sent to the cleanerd when you reflect
changes on the conffile.
Or you want to know the maximum number of checkpoints ?
OK, here I show some calculation for your information:
The maximum number of checkpoints (or snapshots) is, theoretically,
2 ^ 64 - 2 = 1.84467441 .. x 10 ^ 19 (about 18.4 exa checkpoints)
In practice, maximum block count limitation will reach before this.
For example, a 32-bit Linux kernel can handle up to 2 ^ 32 blocks.
Since NILFS2 stores 21 checkpoints in a standard 4KB block, 32-bit
nilfs can handle up to
90,194,313,215 (= about 90.2 giga) checkpoints
If we create a checkpoint per 5 seconds, it corresponds to
18,038,862,643 seconds = 5,010,795 days = 13,728 years
So the conclusion is, you know, up to the capacity of your drive ;)
Cheers,
Ryusuke Konishi
next prev parent reply other threads:[~2009-07-30 14:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-30 4:07 Number of CheckPoints David Fuller
[not found] ` <4A711C80.1040500-ZE272gM1l1AAvxtiuMwx3w@public.gmane.org>
2009-07-30 14:38 ` Ryusuke Konishi [this message]
[not found] ` <20090730.233849.87826385.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-07-30 14:52 ` Ryusuke Konishi
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=20090730.233849.87826385.ryusuke@osrg.net \
--to=ryusuke-sg5x7nla6pw@public.gmane.org \
--cc=dfuller-ZE272gM1l1AAvxtiuMwx3w@public.gmane.org \
--cc=users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.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