From: Ryusuke Konishi <ryusuke-sG5X7nlA6pw@public.gmane.org>
To: users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org,
John-jE24nFfhqzU3hwNNidygWXTaI6DYlTYJ@public.gmane.org
Subject: Re: cleanerd
Date: Thu, 06 Nov 2008 11:50:07 +0900 (JST) [thread overview]
Message-ID: <20081106.115007.82106068.ryusuke@osrg.net> (raw)
In-Reply-To: <491213E2.4010905-jE24nFfhqzU3hwNNidygWXTaI6DYlTYJ@public.gmane.org>
Hi,
On Thu, 06 Nov 2008 10:45:06 +1300, John Huttley wrote:
> Hi,
> my cleanerd stopped again, though I don't see anything in the logs
>
> Is there a way of getting better logging for debugging purposes?
>
> --John
Sorry for inconvenience.
To get better cleanerd logs, change log_priority level specified in
/etc/nilfs_cleanerd.conf as follows:
log_priority info
|
v
log_priority debug
This will make the cleanerd write debug information in syslog.
Note that a HUP signal must be sent to the cleanerd or doing
umount/mount the nilfs partition is required to reflect the change.
Then, if nilfs2 seems to hang during GC, please get a stack dump by
sending the following system request from an active terminal or
console.
# echo t > /proc/sysrq-trigger
This will dump stack information of every kernel thread. The stack
information that contains `nilfs' keywords would give the hint about
which function causes the hang problem.
With regards,
Ryusuke Konishi
next prev parent reply other threads:[~2008-11-06 2:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-05 21:45 cleanerd John Huttley
[not found] ` <491213E2.4010905-jE24nFfhqzU3hwNNidygWXTaI6DYlTYJ@public.gmane.org>
2008-11-06 2:50 ` Ryusuke Konishi [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-10-10 22:18 cleanerd Jan de Kruyf
[not found] ` <ee5afd760910101518u4a85fd0fn6e5539a327b2a876-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-10-11 3:29 ` cleanerd Ryusuke Konishi
[not found] ` <20091011.122911.131278678.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-10-11 5:32 ` cleanerd Jan de Kruyf
[not found] ` <ee5afd760910102232o5f17c50cxb5024f6f76ecbcf5-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-10-11 6:49 ` cleanerd Ryusuke Konishi
[not found] ` <20091011.154916.07997858.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-10-13 19:57 ` cleanerd Jan de Kruyf
2009-10-17 20:47 ` cleanerd Jan de Kruyf
[not found] ` <ee5afd760910171347x4ad27199ka59d0e76f3271050-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-10-19 2:07 ` cleanerd 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=20081106.115007.82106068.ryusuke@osrg.net \
--to=ryusuke-sg5x7nla6pw@public.gmane.org \
--cc=John-jE24nFfhqzU3hwNNidygWXTaI6DYlTYJ@public.gmane.org \
--cc=users-JrjvKiOkagjYtjvyW6yDsg@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