From: dexen deVries <dexen.devries-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Removed checkpoints are still subject to protection period
Date: Wed, 22 Jun 2011 12:59:40 +0200 [thread overview]
Message-ID: <201106221259.40135.dexen.devries@gmail.com> (raw)
Hi,
steps to reproduce:
* create empty filesystem, mount, ensure nilfs_cleanerd is running on it
* configure the nilfs_cleanerd for protection period 3600 (seconds)
* create a bunch of files
* delete the files
* the nilfs_cleanerd does not reclaim space, because checkpoints are protected for 3600 seconds (the expected behavior)
* remove all the snapshots with rmcp
* the problem: the nilfs_cleanerd still does not reclaim space -- it considers the deleted checkpoints as still protected for the duration of 3600 seconds
* once 3600 seconds passes, nilfs_cleanerd normally reclaims space
Expected behavior: cleanerd reclaims diskspace of deleted checkpoints regardless of protection period.
Rationale: there's no user-visible way of accessing deleted checkpoints, so there is no point in keeping them 'round.
tested with linux v3.0-rc4, nilfs-utils v2.0.23
Regards,
--
dexen deVries
[[[↓][→]]]
For example, if the first thing in the file is:
<?kzy irefvba="1.0" rapbqvat="ebg13"?>
an XML parser will recognize that the document is stored in the traditional ROT13 encoding.
(( Joe English, http://www.flightlab.com/~joe/sgml/faq-not.txt ))
--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2011-06-22 10:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-22 10:59 dexen deVries [this message]
[not found] ` <201106221259.40135.dexen.devries-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-06-22 11:04 ` [correction] Re: Removed checkpoints are still subject to protection period dexen deVries
2011-06-23 10:13 ` 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=201106221259.40135.dexen.devries@gmail.com \
--to=dexen.devries-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@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 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.