linux-nilfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vyacheslav Dubeyko <slava-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>
To: Piotr Szymaniak <szarpaj-TbOm9Ca2r9GrDJvtcaxF/A@public.gmane.org>
Cc: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: nilfs2 weird issue - snapshots are gone, cleanerd not running
Date: Mon, 09 Jul 2012 13:28:32 +0400	[thread overview]
Message-ID: <1341826112.1965.6.camel@slavad-ubuntu-11> (raw)
In-Reply-To: <20120709073300.GP1478@wloczykij>

Hi Piotr,

Does system journals on your machines contain any interested details
about reported issue? Could you try to extract some error or warning
messages from system journal?

Thanks,
Vyacheslav Dubeyko.


On Mon, 2012-07-09 at 09:33 +0200, Piotr Szymaniak wrote:
> Hi.
> 
> I've upgraded nilfs-utils (running Gentoo) on 29 july. Today I ran out
> of space on my / and found that nilfs_cleanerd isn't working. When I
> start it from the command line it exits instantly. Also, all previous
> checkpoints on / (also on two other mountpoints on different machine)
> are gone.
> 
> What I did? Downgraded nilfs-utils to 2.1.1, remounted mountpoints. On
> the second machine it's runnig fine (cleaned _all_ checkpoints), on the
> first one with disk space issue it exits just like 2.1.3.
> 
> Here are some fs details. Machine with disk space issues, rootfs:
>     CNO        DATE     TIME  MODE  FLG     NBLKINC       ICNT
>  147688  2012-07-09 08:38:14   cp    -        11075     242915
>  147689  2012-07-09 08:38:14   cp    -           60     242895
> (…)
>  148999  2012-07-09 09:13:46   cp    -           60     242888
>  149000  2012-07-09 09:19:45   cp    -           44     242888
> 
> Filesystem      Size  Used Avail Use% Mounted on
> rootfs           24G   13G   11G  56% /
> 
> mount shows:
> /dev/sda2 on / type nilfs2 (rw,noatime,nodiratime,gcpid=15356)
> 
> There's no nilfs_cleanerd with pid 15356.
> 
> 
> Second machine rootfs:
>    CNO        DATE     TIME  MODE  FLG     NBLKINC       ICNT
>  92246  2012-07-09 08:16:58   cp    -          118      44669
> (…)
>  92439  2012-07-09 09:19:14   cp    -           29      44668
>  92440  2012-07-09 09:19:46   cp    -           33      44668
> 
> Filesystem         Size  Used Avail Use% Mounted on
> rootfs             3.7G  888M  2.6G  26% /
> 
> (it should be around 3G used)
> 
> Second machine second mountpoint:
>    CNO        DATE     TIME  MODE  FLG     NBLKINC       ICNT
>   1496  2012-07-09 03:31:23   cp    -         8837     132766
>   1497  2012-07-09 03:31:26   cp    -          468     132766
>   1498  2012-07-09 03:41:27   cp    -         1474     132765
> 
> (this fs should containt *all* 1498 checkpoints)
> 
> Filesystem         Size  Used Avail Use% Mounted on
> /dev/dm-2          117G   58G   54G  76% /mnt/home_backup
> 
> (in this one it should be around 100G of used space)
> 
> mount:
> /dev/dm-2 on /mnt/home_backup type nilfs2 (rw,gcpid=13135)
> /dev/sda3 on / type nilfs2 (rw,noatime,nodiratime,gcpid=1363)
> 
> Both cleaners running (the second mountpoint - /mnt/home_backup - is under
> heavy load and I suppose it will end with around 20G used space).
> 
> Where to go from this point? How to debug nilfs_cleanerd issue?
> 
> 
> Piotr Szymaniak.


--
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

  reply	other threads:[~2012-07-09  9:28 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 [this message]
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
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=1341826112.1965.6.camel@slavad-ubuntu-11 \
    --to=slava-yeenwd64clxbdgjk7y7tuq@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).