Skip to contentSkip to conversation

Removed checkpoints are still subject to protection period

DISCUSSION dexen deVries 2 participants 3 messages Jun 22, 2011 – Jun 23, 2011 1 message not in the archive NILFS2 filesystem

lore
Share & tools
lore
#0 lore 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,

Signature · 13 lines
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 [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

A message that is not in the archive (sent off-list or not yet received): 201106221259.40135.dexen.devries-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org

#2 lore raw

Oops,

Quoted 1 line · On Wednesday 22 of June 2011 12:59:40 dexen wrote:

* remove all the snapshots with rmcp

should be:
* remove all the checkpoints with rmcp

Regards,

Signature · 13 lines
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 [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
#3 lore raw
In reply to a message not in the archive
Quoted 14 lines · dexen deVries
Quoted 13 lines

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

Quoted 6 lines
Quoted 3 lines

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.
* remove all the snapshots with rmcp

should be:
* remove all the checkpoints with rmcp

Yes, we know these issues and I feel rmcp and cleanerd should coordinate better. I'll think of them for nilfs-utils-2.1 though I cannot make any guaranttes now.

Thank you for devoted feedbacks,

Ryusuke Konishi

Quoted 18 lines

tested with linux v3.0-rc4, nilfs-utils v2.0.23

Regards,

Signature · 13 lines
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 [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html