On Mon, 21 Mar 2011 13:05:48 +0100, dexen deVries wrote: > Hi again, > > > On Monday 21 of March 2011 12:07:06 you wrote: > > The ".nilfs" file is used for two purposes: > > > > 1) As the file on which the nilfs library issues ioctls. > > > > 2) For advisory locks (i.e. fcntl(F_GETLK/F_SETLK/FSETLKW)). This > > works as a mutex between the cleaner and other nilfs-tools. > > > Regarding 2), it seems multiple instances of nilfs_cleanerd can be started for > one filesystem (which leads to metadata corruption, as per my earlier > ``Regarding problem with nilfs_cleanerd - part 2 and Nilfs_cleanerd err=-17'' > mail). > > Is that intentional? Should we guard on nilfs_cleanerd level, or on kernel > level? Even if multiple nilfs_cleanerd were invoked on a nilfs volume, they work exclusively and corruption will not occur. Of course, mount.nilfs2 does not invoke multiple cleaners unless user intentionally do so. I guess the corruption problem is caused by some sort of difficult-to-find bug at this time. Thanks, Ryusuke Konishi -- To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
