From: dexen deVries <dexen.devries-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: One checkpoint just won't get GC'd
Date: Thu, 17 Feb 2011 15:29:43 +0100 [thread overview]
Message-ID: <201102171529.43904.dexen.devries@gmail.com> (raw)
Hello,
I have a few snapshots and between two of them (few days old) there is a lone
checkpoint (68) that just won't get GC'd:
CNO DATE TIME MODE FLG NBLKINC ICNT
67 2011-02-11 10:58:34 ss - 10214 183442
68 2011-02-11 11:00:07 cp - 12 183442
11205 2011-02-11 13:13:44 ss - 2229 245061
40205 2011-02-16 18:16:04 ss - 59 260421
Lots and lots of subsequent checkpoints has been GC'd sine then; current is
79450.
How do I pinpoint the reason the checkpoint is not getting GC'd?
Running Linux 2.6.38-rc4 with nilfs-utils-2.0.21 right now, but the checkpoint
and the snapshots around it were created with 2.6.37 and nilfs-utils-2.0.20,
IIRC.
--
dexen deVries
[[[↓][→]]]
> how does a C compiler get to be that big? what is all that code doing?
iterators, string objects, and a full set of C macros that ensure
boundary conditions and improve interfaces.
ron minnich, in response to Charles Forsyth
http://9fans.net/archive/2011/02/90
--
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
next reply other threads:[~2011-02-17 14:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-17 14:29 dexen deVries [this message]
[not found] ` <201102171529.43904.dexen.devries-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-02-18 2:22 ` One checkpoint just won't get GC'd Ryusuke Konishi
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=201102171529.43904.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.