All of lore.kernel.org
 help / color / mirror / Atom feed
From: dexen deVries <dexen.devries-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: One checkpoint doesn't get GC'd
Date: Thu, 17 Nov 2011 13:05:47 +0100	[thread overview]
Message-ID: <201111171305.49635.dexen.devries@gmail.com> (raw)
In-Reply-To: <20111116.011102.126207784.ryusuke-sG5X7nlA6pw@public.gmane.org>

Hi Ryusuke,


On Tuesday 15 of November 2011 17:11:02 you wrote:
> This may happen since garbage collection of nilfs is done for each
> disk segment instead of checkpoint.
> 
> If GC did not reclaim any blocks for a checkpoint, the checkpoint will
> survive transiently.

Thanks for clarification. I've always assumed that GC just removes checkpoints 
in natural order; good to see it's smarter than that ;-)

The CP got GC'd recently alright.


Cheers,
-- 
dexen deVries

[[[↓][→]]]

``As my friend Jacob Gabrielson once put it, advocating Object-Oriented 
Programming is like advocating Pants-Oriented Clothing.''
 -- Steve Yegge, in
http://steve-yegge.blogspot.com/2006/03/execution-in-kingdom-of-nouns.html
--
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

      parent reply	other threads:[~2011-11-17 12:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-14 12:51 One checkpoint doesn't get GC'd dexen deVries
     [not found] ` <201111141351.50798.dexen.devries-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-11-15 16:11   ` Ryusuke Konishi
     [not found]     ` <20111116.011102.126207784.ryusuke-sG5X7nlA6pw@public.gmane.org>
2011-11-17 12:05       ` dexen deVries [this message]

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=201111171305.49635.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.