Hi all,
and thanks a lot for your work on NILFS2. It's wonderful.
I'm using it for my /home, and it works good.
Today I tried to change checkpoint interval using nilfs-tune.Â
So, nilfs-tune -l gives me:
nilfs-tune 2.1.0-rc1
Filesystem volume name: home
Filesystem UUID: b22b2da4-be32-4e0c-ba33-1adeff256e2f
Filesystem magic number: 0x3434
Filesystem revision #: 2.0
Filesystem features: (none)
Filesystem state: invalid or mounted
Filesystem OS type: Linux
Block size: 2048
Filesystem created: Mon Jun 6 19:55:33 2011
Last mount time: Wed Jun 8 18:40:20 2011
Last write time: Wed Jun 8 18:48:16 2011
Mount count: 20
Maximum mount count: 50
Reserve blocks uid: 0 (user root)
Reserve blocks gid: 0 (group root)
First inode: 11
Inode size: 128
DAT entry size: 32
Checkpoint size: 192
Segment usage size: 16
Number of segments: 35678
Device size: 149648572416
First data block: 2
# of blocks per segment: 2048
Reserved segments %: 1
Last checkpoint #: 50352
Last block address: 50374721
Last sequence #: 24583
Free blocks count: 22718464
Commit interval: 20
# of blks to create seg: 0
CRC seed: 0x8987044d
CRC check sum: 0xc50b9714
CRC check data size: 0x00000118
But it doesn't care... I can change 'Commit interval' in any way,
but when I mount it I see this:
[ 2366.096819] segctord starting. Construction interval = 0 seconds,
CP frequency < 30 seconds
[ 2535.082421] segctord starting. Construction interval = 0 seconds,
CP frequency < 30 seconds
So, I have continuos checkpoint, like this:
lscp|tail
50244 2011-06-08 18:45:22 cp - 141 600277
50245 2011-06-08 18:45:22 cp - 41 600277
50246 2011-06-08 18:45:22 cp - 57 600277
50247 2011-06-08 18:45:23 cp - 5884 600277
50248 2011-06-08 18:45:23 cp - 7736 600277
50249 2011-06-08 18:45:23 cp - 747 600276
I've tried stock Ubuntu kernel, also, but it's always the same.
Thanks a lot for your time,
Andrea
---------------------
 I'm using latest git tree for nilfs tools and kernel.
--
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
