From: Dave <dave-/hCUnnzDXf0AvxtiuMwx3w@public.gmane.org>
To: users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org
Subject: Nilfs features
Date: Mon, 25 May 2009 13:46:14 +0400 [thread overview]
Message-ID: <4A1A68E6.50905@0bits.com> (raw)
Hi,
I converted (backup/restore) my home directory onto nilfs2 to test it in
anger (yes i know the caveats about it corrupting all my data, etc, but
i'm willing to restore when required).
When restoring the data onto a nilfs2 filesystem there really is no
requirement to have the checkpointing running as you have a good copy
from your tar, cpio archive that you are restoring from. So is there a
way to temporarily suspend checkpointing with a command and then restart
it after the restore has completed ? I think this would be useful also
for when you want to have a 'privacy' mode (like firefox/mozilla) where
you can suspend checkpointing, start some confidential work, email,
browsing etc, and then restart checkpointing and roll back to the
previous state.
In addition to this there doesn't seem to be a way to delete a range of
checkpoints. When i did my restore from my archive, i generated 700+
useless checkpoints which i had to delete one by one (in a script). It
would be nice to have a 'rmcp 1-100' or 'rmcp -100' or 'rmcp 100-' to
delete a checkpoint range, a start to end.
Also it seems for home directories, a 5 second checkpointing seems
exessive. In 14hrs i have 10,000 checkpoints (even when seemingly idle
with mozilla page refreshes, dovecot index files updates for email, etc).
home:~$ uptime
13:35:09 up 14:29, 7 users, load average: 0.85, 1.76, 2.07
home:~$ lscp|tail
10342 2009-05-25 13:34:31 cp i 6698 323163
10343 2009-05-25 13:34:36 cp - 6761 323163
10344 2009-05-25 13:34:41 cp i 6702 323163
10345 2009-05-25 13:34:45 cp - 29 323163
10346 2009-05-25 13:34:46 cp i 6679 323163
10347 2009-05-25 13:34:51 cp i 6669 323163
10348 2009-05-25 13:34:56 cp i 6675 323163
10349 2009-05-25 13:35:01 cp i 6676 323163
10350 2009-05-25 13:35:06 cp i 6649 323163
10351 2009-05-25 13:35:11 cp i 6679 323163
It would also be nice to change the cp/clean interval without editing
the conf file, perhaps during the nite we can had different checkpoint
intervals and during work a smaller cp interval.
Finally instead of having 5 commands, it'd be nice to have once command
with different options (like zfs). So instead have
. nilfs checkpoint
. nilfs snapshot
. nilfs remove
. nilfs list
. nilfs suspend
. nilfs restart
etc...
All seems to be working fine so far, so take this as constructive comments.
Cheers
Dave
next reply other threads:[~2009-05-25 9:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-25 9:46 Dave [this message]
[not found] ` <4A1A68E6.50905-/hCUnnzDXf0AvxtiuMwx3w@public.gmane.org>
2009-05-25 23:20 ` Nilfs features Ryusuke Konishi
[not found] ` <20090526.082051.100027806.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-05-26 4:54 ` Dave
2009-05-31 16:20 ` Ryusuke Konishi
[not found] ` <20090601.012057.21016829.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-06-02 8:21 ` Dave
[not found] ` <4A24E100.8040204-/hCUnnzDXf0AvxtiuMwx3w@public.gmane.org>
2009-06-02 9:23 ` Ryusuke Konishi
-- strict thread matches above, loose matches on Subject: below --
2009-05-30 3:44 Jérôme Poulin
[not found] ` <debc30fc0905292044r311a2842j53832195d0ef88bd-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-06-02 8:31 ` Dave
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=4A1A68E6.50905@0bits.com \
--to=dave-/hcunnzdxf0avxtiumwx3w@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 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.