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@xxxxxxxxxxxxx>
> ---
> (...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@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
