On Sun, Jun 21, 2009 at 04:44:19PM +0300, Sami Liedes wrote: > I *think* I might know what the problem is. The nilfs2-tools in Debian > unstable is 2.0.12, while the version of nilfs2 in 2.6.30 is .14 > unless I'm mistaken.
Never mind, I just realized 2.0.12 is the latest -tools.
You say I should start the cleanerd by running
# nilfs_cleanerd /dev/sdb1 /
However nothing in the output of `nilfs_cleanerd -h' indicates
anything of the second parameter (mount point). Looking at the source,
that's how mount.nilfs2 runs it too, and that's exactly the case where
it fails.
Running merely `nilfs_cleanerd /dev/mapper/lacie', as per the
nilfs_cleanerd -h output, succeeds (but I don't know if it does the
right thing). When I (or mount) gives the mount point as a second
parameter, it fails fairly silently. I only get this in
/var/log/daemon.log:
When started by mount.nilfs2:
------------------------------------------------------------
Jun 20 20:34:28 lh nilfs_cleanerd[27527]: start
Jun 20 20:34:28 lh nilfs_cleanerd[27527]: cannot create cleanerd on
/dev/mapper/lacie
Jun 20 20:34:28 lh nilfs_cleanerd[27527]: shutdown
------------------------------------------------------------
When started manually by running `nilfs_cleanerd /dev/mapper/lacie
/media/lacie' (the mount point):
------------------------------------------------------------
Jun 21 16:12:04 lh nilfs_cleanerd[2573]: start
Jun 21 16:12:04 lh nilfs_cleanerd[2573]: cannot create cleanerd on
/dev/mapper/lacie
Jun 21 16:12:04 lh nilfs_cleanerd[2573]: shutdown
------------------------------------------------------------
Sami
signature.asc
Description: Digital signature
_______________________________________________ users mailing list [email protected] https://www.nilfs.org/mailman/listinfo/users
