All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave <dave-/hCUnnzDXf0AvxtiuMwx3w@public.gmane.org>
To: NILFS Users mailing list
	<users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org>,
	ryusuke-sG5X7nlA6pw@public.gmane.org
Subject: Re: Nilfs features
Date: Tue, 02 Jun 2009 12:21:20 +0400	[thread overview]
Message-ID: <4A24E100.8040204@0bits.com> (raw)
In-Reply-To: <20090601.012057.21016829.ryusuke-sG5X7nlA6pw@public.gmane.org>

On 05/31/09 20:20, Ryusuke Konishi wrote:
> Hi,
> On Tue, 26 May 2009 08:20:51 +0900 (JST), Ryusuke Konishi wrote:
>> Hi,
>> On Mon, 25 May 2009 13:46:14 +0400, Dave wrote:
>>> 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.
>> Okay, I'll take in this in some form.
> 
> For the moment, I've added this feature and pushed it into the git
> tree.
> 
> (Instead of '1-100', '-100', or '10..', I took notation like '1..100',
>  '..100', or '10..' respectively, according to the git tool)
> 
> If you would like to try it soon, please see
> 
>  http://www.nilfs.org/git/
> 
> for download/build information.
> 
> I'll include it in the next release of the utility package.
> 

Hi Ryusuke,

I've tried this and it seems to work perfectly. Thanks for the quick 
feature addition.

It seems that i still have to wait for cleanerd to kick in to reclaim 
the space even though i clearly cannot get to a checkpoint i've just 
deleted. I believe we should reclaim immediately (but perhaps this is 
harder to implement)...


bash-3.2# df -h .
Filesystem            Size  Used Avail Use% Mounted on
/dev/sdb2              39G  9.0G   28G  25% /home
bash-3.2# cp /shared/1gb .
bash-3.2# df -h .
Filesystem            Size  Used Avail Use% Mounted on
/dev/sdb2              39G   10G   27G  28% /home
bash-3.2# lscp | tail
               155133  2009-06-02 12:12:27   cp    i       6662     253255
               155134  2009-06-02 12:12:29   cp    -         35     253255
               155135  2009-06-02 12:12:32   cp    i       6622     253255
               155136  2009-06-02 12:12:37   cp    i       6587     253255
               155137  2009-06-02 12:12:42   cp    i       6654     253255
               155138  2009-06-02 12:12:47   cp    i       6744     253255
               155139  2009-06-02 12:12:52   cp    i       6524     253255
               155140  2009-06-02 12:12:57   cp    i       6762     253255
               155141  2009-06-02 12:13:02   cp    i       6670     253255
               155142  2009-06-02 12:13:07   cp    -       6748     253255
bash-3.2# rm 1gb
bash-3.2# df -h .
Filesystem            Size  Used Avail Use% Mounted on
/dev/sdb2              39G   10G   27G  28% /home
bash-3.2# lscp|tail
               155151  2009-06-02 12:13:29   cp    -         35     253188
               155152  2009-06-02 12:13:35   cp    -        237     253229
               155153  2009-06-02 12:13:37   cp    -       6334     253238
               155154  2009-06-02 12:13:42   cp    -       8380     253255
               155155  2009-06-02 12:13:47   cp    i       7987     253255
               155156  2009-06-02 12:13:52   cp    i       3743     253255
               155157  2009-06-02 12:13:57   cp    i       8092     253255
               155158  2009-06-02 12:14:02   cp    i       7991     253255
               155159  2009-06-02 12:14:07   cp    i       7986     253255
               155160  2009-06-02 12:14:12   cp    -       9129     253254
bash-3.2# rmcp ..155160
bash-3.2# lscp|tail
                  CNO        DATE     TIME  MODE  FLG   NBLKINC       ICNT
               155161  2009-06-02 12:14:17   cp    i       6839     253254
               155162  2009-06-02 12:14:22   cp    i       7012     253254
               155163  2009-06-02 12:14:27   cp    -       6886     253255
               155164  2009-06-02 12:14:29   cp    -         51     253254
               155165  2009-06-02 12:14:32   cp    i       6737     253254
               155166  2009-06-02 12:14:37   cp    i       2618     253254
bash-3.2# df -h .
Filesystem            Size  Used Avail Use% Mounted on
/dev/sdb2              39G   10G   27G  28% /home



much appreciated.
Dave

  parent reply	other threads:[~2009-06-02  8:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-25  9:46 Nilfs features Dave
     [not found] ` <4A1A68E6.50905-/hCUnnzDXf0AvxtiuMwx3w@public.gmane.org>
2009-05-25 23:20   ` 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 [this message]
     [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=4A24E100.8040204@0bits.com \
    --to=dave-/hcunnzdxf0avxtiumwx3w@public.gmane.org \
    --cc=ryusuke-sG5X7nlA6pw@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.