linux-nilfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: dexen deVries <dexen.devries-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: Piotr Szymaniak <szarpaj-TbOm9Ca2r9GrDJvtcaxF/A@public.gmane.org>
Subject: Re: nilfs2 weird issue - snapshots are gone, cleanerd not running
Date: Mon, 09 Jul 2012 11:33:13 +0200	[thread overview]
Message-ID: <10181027.pPHs7IDARt@coil> (raw)
In-Reply-To: <20120709073300.GP1478@wloczykij>

On Monday 09 of July 2012 09:33:00 you wrote:
>(...)
> Where to go from this point? How to debug nilfs_cleanerd issue?

using strace -f  on the nilfs_cleanerd should give you a clue what causes the 
exit. it may exit if can't connect to syslogd.


if `lscp' reports no checkpoints, try `lscp -a' -- should show even minor 
checkpoints (which are checkpoints created by GC, AFAIK).

-- 
dexen deVries

[[[↓][→]]]

"all dichotomies are either true or false" is a true paradox because it's 
paradoxical only if it is a paradox ;)
--
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

  parent reply	other threads:[~2012-07-09  9:33 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-09  7:33 nilfs2 weird issue - snapshots are gone, cleanerd not running Piotr Szymaniak
2012-07-09  9:28 ` Vyacheslav Dubeyko
2012-07-09 16:56   ` Piotr Szymaniak
2012-07-09 18:55     ` Vyacheslav Dubeyko
     [not found]       ` <51D5FCEA-7103-4D4A-BADA-99A9780D9B68-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>
2012-07-10  1:53         ` Ryusuke Konishi
     [not found]           ` <20120710.105315.33988123.konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
2012-07-10  7:18             ` Vyacheslav Dubeyko
2012-07-10  8:51               ` Ryusuke Konishi
     [not found]                 ` <20120710.175131.21311203.konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
2012-07-10 10:38                   ` Vyacheslav Dubeyko
2012-07-10 11:09                     ` Ryusuke Konishi
     [not found]                       ` <20120710.200937.163315083.konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
2012-07-10 14:07                         ` Piotr Szymaniak
2012-07-10 16:40                           ` Ryusuke Konishi
     [not found]                             ` <20120711.014049.157490457.konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
2012-07-12 11:42                               ` Piotr Szymaniak
2012-07-09  9:33 ` dexen deVries [this message]
2012-07-09  9:49   ` Vyacheslav Dubeyko
2012-07-10  7:51   ` Piotr Szymaniak
2012-07-10  8:34     ` Vyacheslav Dubeyko
2012-07-10  9:50       ` Piotr Szymaniak
2012-07-10 10:43         ` Vyacheslav Dubeyko
2012-07-10  9:52     ` Piotr Szymaniak
  -- strict thread matches above, loose matches on Subject: below --
2012-07-09 10:31 Vyacheslav Dubeyko

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=10181027.pPHs7IDARt@coil \
    --to=dexen.devries-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=szarpaj-TbOm9Ca2r9GrDJvtcaxF/A@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).