From: Andrea Gelmini <andrea.gelmini-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org
Subject: Re: Problem setting CP interval
Date: Thu, 9 Jun 2011 16:11:24 +0200 [thread overview]
Message-ID: <BANLkTimA3C9rCnsEHuCVwpx1DcB-a0757A@mail.gmail.com> (raw)
In-Reply-To: <BANLkTim7Dp7-U1ee1hm7EWpw5We+pPBjAw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1300 bytes --]
2011/6/8 Andrea Gelmini <andrea.gelmini-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>:
Hi all,
and thanks a lot for your time.
> 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
I made a stupid script to replicate my problem.
Results are the same, using different kernel, and so on.
I also tried different version of nilfs-tools, picking via git
since commit that introduce nilfs-tune.
You have just to run it as root (give it a look, before):
root@dell:/home/gelma/dev/prg# bash test_nilf.sh
0+0 records in
0+0 records out
0 bytes (0 B) copied, 3.506e-05 s, 0.0 kB/s
mkfs.nilfs2 (nilfs-utils 2.1.0-rc1)
Start writing file system initial data to the device
Blocksize:4096 Device:/dev/loop0 Device Size:1073741824
File system initialization succeeded !!
[ 623.103552] segctord starting. Construction interval = 5 seconds,
CP frequency < 30 seconds
nilfs-tune 2.1.0-rc1
[ 624.212073] segctord starting. Construction interval = 0 seconds,
CP frequency < 30 seconds
Thanks a lot for your time,
Andrea
[-- Attachment #2: test_nilf.sh --]
[-- Type: application/x-sh, Size: 501 bytes --]
next prev parent reply other threads:[~2011-06-09 14:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-08 16:53 Problem setting CP interval Andrea Gelmini
[not found] ` <BANLkTim7Dp7-U1ee1hm7EWpw5We+pPBjAw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-06-09 14:11 ` Andrea Gelmini [this message]
[not found] ` <BANLkTimA3C9rCnsEHuCVwpx1DcB-a0757A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-06-09 15:41 ` Ryusuke Konishi
[not found] ` <20110610.004125.192724285.ryusuke-sG5X7nlA6pw@public.gmane.org>
2011-06-09 16:20 ` 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=BANLkTimA3C9rCnsEHuCVwpx1DcB-a0757A@mail.gmail.com \
--to=andrea.gelmini-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).