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: One checkpoint doesn't get GC'd
Date: Mon, 14 Nov 2011 13:51:50 +0100	[thread overview]
Message-ID: <201111141351.50798.dexen.devries@gmail.com> (raw)

Hi,


I have strange problem: one checkpoint doesn't get garbage-collected, in spite 
of subsequent checkpoints getting GC'd just alright.

for example:
1170140  2011-10-14 09:34:17   cp    -           50     379222
1171655  2011-10-14 14:43:14   cp    -         1345     379479
1171663  2011-10-14 14:45:06   cp    -           54     379480
1171664  2011-10-14 14:45:17   cp    -           51     379479
(...)

A few hours ago there were much more checkpoints between 1170140 and 1171655 
and they all got GC'd as expected -- but not the 1170140 itself.

For reference,
kernel: 3.1.0 (stock)
nilfs-utils: 2.1.0-rc1


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

             reply	other threads:[~2011-11-14 12:51 UTC|newest]

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

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