From: mikael-m2T68/X/qvZAfugRpC6u6w@public.gmane.org
To: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: nilfs_cleanerd not running
Date: Tue, 30 Aug 2016 22:01:09 +0200 [thread overview]
Message-ID: <2a90bda59a98d4f35e8dbab5534c014e@fripost.org> (raw)
Hi,
It seems my NILFS is not garbage collected. The other day I was not able
to boot up my NixOS due to a full disk. I booted on a USB stick and ran
nilfs-clean which freed about 20 Gbytes. I suppose there should always
be a process nilfs_cleanerd running on a system in order to clean up old
check points. I have actually not read on the NILFS web site that
nilfs_cleanerd should be running normally, but maybe I have missed this.
Should it not be running normally?
When I am running nilfs-clean on my device, I get:
'No cleaner found on /dev/dm-0.'
mount | grep nilfs gives:
/dev/mapper/cryptroot on / type nilfs2 (rw,relatime)
/dev/mapper/cryptroot on /nix/store type nilfs2 (ro,relatime)
nilfs-clean -V gives:
nilfs-clean version 2.2.3
I am only able to run nilfs_cleanerd after setting LD_LIBRARY_PATH to
/nix/store/*-nilfs-utils-2.2.3/lib
nilfs_cleanerd /dev/mapper/cryptroot
NILFS_CLEANERD_PID=24468
It seems however like the process terminates since there does not seem
to exist any process when running 'ps aux | grep nilfs'
When trying 'sudo mount -t nilfs2 -o remount,pp=1 /dev/mapper/cryptroot
/', I get:
/nix/store/y0ldq0j9qpax23d6g5iww7nz17xgx32q-nilfs-utils-2.2.3/sbin/nilfs_cleanerd:
error while loading shared libraries: libnilfs.so.0: cannot open shared
object file: No such file or directory
mount.nilfs2: Warning: cannot get pid of cleanerd
mount.nilfs2: cannot modify /etc/mtab.
Please remount the partition with -f option after making /etc/mtab
writable.
I am running NixOS 16.03
'uname -r' gives:
4.4.14
Any ideas?
Thanks in advance.
Kind regards,
Mikael Andersson
--
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
next reply other threads:[~2016-08-30 20:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-30 20:01 mikael-m2T68/X/qvZAfugRpC6u6w [this message]
[not found] ` <2a90bda59a98d4f35e8dbab5534c014e-m2T68/X/qvZAfugRpC6u6w@public.gmane.org>
2016-08-30 22:28 ` nilfs_cleanerd not running mikael-m2T68/X/qvZAfugRpC6u6w
[not found] ` <ef82ce0808205f8ecda06baa9a3f9232-m2T68/X/qvZAfugRpC6u6w@public.gmane.org>
2016-08-31 4:27 ` Ryusuke Konishi
2016-08-31 4:03 ` 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=2a90bda59a98d4f35e8dbab5534c014e@fripost.org \
--to=mikael-m2t68/x/qvzafugrpc6u6w@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