From: dexen deVries <dexen.devries-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] nilfs2: record used amount of each checkpoint in checkpoint list
Date: Tue, 1 Mar 2011 13:05:42 +0100 [thread overview]
Message-ID: <201103011305.43120.dexen.devries@gmail.com> (raw)
In-Reply-To: <1298740431-13749-1-git-send-email-konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
Hello,
On Saturday 26 of February 2011 18:13:51 you wrote:
> This records the number of used blocks per checkpoint in each
> checkpoint entry of cpfile. Even though userland tools can get the
> block count via nilfs_get_cpinfo ioctl, it was not updated by the
> nilfs2 kernel code. This fixes the issue and makes it available for
> userland tools to calculate used amount per checkpoint.
>
> Signed-off-by: Ryusuke Konishi <konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
> ---
> (...snip...)
I've applied this this patch and the two recent userpace patches and it works
alright, with one surprise -- two suspiciously large BLKCNT:
$ lscp -b
(...snip...)
270584 2011-03-01 12:52:57 cp - 33 248244
270585 2011-03-01 12:53:01 cp - 34 248245
270586 2011-03-01 12:53:06 cp - 18446744073709550523
248245
270587 2011-03-01 12:53:11 cp - 18446744073709550550
248257
270588 2011-03-01 12:53:15 cp - 1268 248247
270589 2011-03-01 12:53:16 cp - 1803 248246
270590 2011-03-01 12:53:21 cp - 4952 248256
(...snip...)
It is possible the two strange checkpoints (270586 & 7) were created with new
userland and old kernel, before reboot.
Do you want me to provide any extra info on it or just let it slip?
--
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 prev parent reply other threads:[~2011-03-01 12:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-26 17:13 [PATCH] nilfs2: record used amount of each checkpoint in checkpoint list Ryusuke Konishi
[not found] ` <1298740431-13749-1-git-send-email-konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
2011-03-01 12:05 ` dexen deVries [this message]
[not found] ` <201103011305.43120.dexen.devries-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-03-02 1:49 ` Ryusuke Konishi
2011-03-04 7:56 ` Jiro SEKIBA
[not found] ` <87hbbjpbdp.wl%jir-27yqGEOhnJbQT0dZR+AlfA@public.gmane.org>
2011-03-04 10:38 ` Ryusuke Konishi
[not found] ` <20110304.193857.78339919.ryusuke-sG5X7nlA6pw@public.gmane.org>
2011-03-04 15:17 ` 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=201103011305.43120.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.