Skip to contentSkip to conversation

nilfs_cleanerd doesn't get started when /etc/mtab is a symlink

DISCUSSION Eric Sandeen 2 participants 2 messages Jun 16, 2011 – Jun 17, 2011 1 message not in the archive NILFS2 filesystem

lore
Share & tools
lore
#0 lore raw

https://bugzilla.redhat.com/show_bug.cgi?id=701735

From the bug:

Quoted 7 lines
# mount -t nilfs2 /dev/nbd1 /media/fedora/src
mount.nilfs2: cannot modify /etc/mtab.
Please remount the partition with -f option after making /etc/mtab writable.
nilfs_cleanerd not started

But /etc/mtab is now a symlink, which just exists for the benefit of legacy code which expects to be able to read it.

Any suggestions? (/etc/mtab is now a symlink to /proc/partitions)

Thanks,
-Eric
--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html

A message that is not in the archive (sent off-list or not yet received): [email protected]

#2 lore raw

Hi Eric,

Quoted 9 lines · Eric Sandeen

https://bugzilla.redhat.com/show_bug.cgi?id=701735

From the bug:

Quoted 5 lines
# mount -t nilfs2 /dev/nbd1 /media/fedora/src
mount.nilfs2: cannot modify /etc/mtab.
Please remount the partition with -f option after making /etc/mtab writable.
nilfs_cleanerd not started
Quoted 4 lines
Quoted 2 lines

But /etc/mtab is now a symlink, which just exists for the benefit of legacy code which expects to be able to read it.

Any suggestions? (/etc/mtab is now a symlink to /proc/partitions)

Thank you for letting me know this.

The problem is mount/umount helper programs of nilfs2 are using a few userspace mount options like "uhelper=" option; these userspace options ("gcpid=", "pp=", and "nogc" options in the case of nilfs) required modifying mtab.

I will consider eliminating them before upcoming nilfs-utils-2.1 release.

Thanks,
Ryusuke Konishi
--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html