linux-nilfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ryusuke Konishi <konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
To: dennis.murata-uxC5H9eHYlcAvxtiuMwx3w@public.gmane.org,
	lennart-mdGvqq1h2p+GdvJs77BJ7Q@public.gmane.org
Cc: systemd-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
	linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [systemd-devel] nilfs-cleanerd startup on boot
Date: Wed, 04 Mar 2015 09:18:16 +0900	[thread overview]
Message-ID: <54F64F48.80403@lab.ntt.co.jp> (raw)
In-Reply-To: <HKNPR03MB452F1AE0C164650CE0CCCA4ED110-prId2LJ51aXRkCEQwRequ+O6mTEJWrR4XA4E9RH9d+qIuWR1G4zioA@public.gmane.org>

Hi

On 2015/03/04 0:44, dennis.murata-uxC5H9eHYlcAvxtiuMwx3w@public.gmane.org wrote:
> I had mis-typed the address for the nilfs mail group
>
>> -----Original Message-----
>> From: Lennart Poettering [mailto:lennart-mdGvqq1h2p+GdvJs77BJ7Q@public.gmane.org]
>> Sent: Saturday, February 28, 2015 12:34 PM
>> To: Dennis Murata (WT01 - ENU)
>> Cc: systemd-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org; linus-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
>> Subject: Re: [systemd-devel] nilfs-cleanerd startup on boot
>>
>> On Fri, 27.02.15 18:31, dennis.murata-uxC5H9eHYlcAvxtiuMwx3w@public.gmane.org
>> (dennis.murata-uxC5H9eHYlcAvxtiuMwx3w@public.gmane.org) wrote:
>>
>>> I have a fedora 21 system that where I mount an nilfs2 file system.
>>> I use a simple /etc/modules-load.d/nilfs.conf file to load the kernel
>>> module and have an entry in the fstab.
>>
>> Creating the modules-load.d snippet should not be necessary, as the kernel
>> should autoload the kernel module for it when it is first required.
> I did not find this to be the case for fedora 21.
 > Without creating the file to load the module, any attempt I made to mount
 > the file system would get a unknown filetype error.  Does this point at
 > adding this module to the initrd file?

Is "nilfs2.ko" installed in your environment?

Try "modinfo nilfs2"

Older fedora needed kernel-modules-extra package. [1]

[1] http://nilfs.sourceforge.net/en/pkg_fedora.html

>>> The file system mounts on boot as it should, but the nilfs-cleanerd
>>> program does not startup.  If I umount /nilfs then mount /nilfs the
>>> nilfs-cleanerd program starts as it should to cleanup the checkpoints.
>>
>> How is that daemon supposed to be started? Is it forked off /bin/mount?
>>
>>> Does systemd use a different mount program at boot?
>>
>> It uses /bin/mount for mounting normal file systems.

nilfs_cleanerd is invoked through /sbin/mount.nilfs2 helper. [2]
The helper is called from /sbin/mount if it exists.

/sbin/mount.nilfs2 is included in nilfs-utils package.

nilfs_cleanerd is just a user-land process, so it can be
manually invoked if you have root privilege. [3]

   # /sbin/nilfs_cleanerd <device> <directory>

But, in this case, you need to kill nilfs_cleanerd
manually before umount.  So, I recommend running cleanerd
through mount.nilfs2.

The above explanation may not suit for the recent fedora
since nilfs-utils is not yet tuned to systemd environment.

[2] http://nilfs.sourceforge.net/en/man8/mount.nilfs2.8.html
[3] http://nilfs.sourceforge.net/en/man8/nilfs_cleanerd.8.html

Regards,
Ryusuke Konishi

>>> Is there something else that should be included other than the
>>> nilfs.conf file?  I have just started using a system with systemd as
>>> the init so please forgive my ignorance.
>>
>> I have no idea about nilfs really, and we had no reports about any problems
>> with it before.
> I wanted to look at the performance of nilfs and f2fs.
 > This is my first try at using these file systems
>>
>> Lennart
>>
>> --
>> Lennart Poettering, Red Hat
> --
> 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

--
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:[~2015-03-04  0:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <SIXPR03MB461887A763AD9ADA7B79841ED150@SIXPR03MB461.apcprd03.prod.outlook.com>
     [not found] ` <20150228183348.GA8274@gardel-login>
2015-03-03 15:44   ` nilfs-cleanerd startup on boot dennis.murata
     [not found]     ` <HKNPR03MB452F1AE0C164650CE0CCCA4ED110-prId2LJ51aXRkCEQwRequ+O6mTEJWrR4XA4E9RH9d+qIuWR1G4zioA@public.gmane.org>
2015-03-04  0:18       ` Ryusuke Konishi [this message]
2015-03-04  1:11         ` dennis.murata
     [not found]           ` <SIXPR03MB461D49AB19D08CF73F05760ED1E0-vZpGLg/9lRlECMeiuiIiL+O6mTEJWrR4XA4E9RH9d+qIuWR1G4zioA@public.gmane.org>
2015-03-04  3:45             ` [systemd-devel] " Ryusuke Konishi
2015-03-04 21:13           ` Kai Krakow

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=54F64F48.80403@lab.ntt.co.jp \
    --to=konishi.ryusuke-zyj7fxus5i5l9jvzuh4aog@public.gmane.org \
    --cc=dennis.murata-uxC5H9eHYlcAvxtiuMwx3w@public.gmane.org \
    --cc=lennart-mdGvqq1h2p+GdvJs77BJ7Q@public.gmane.org \
    --cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=systemd-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@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).