From: Ryusuke Konishi <konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
To: sandeen-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
Cc: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: nilfs_cleanerd doesn't get started when /etc/mtab is a symlink
Date: Sat, 18 Jun 2011 01:08:58 +0900 (JST) [thread overview]
Message-ID: <20110618.010858.91423049.ryusuke@osrg.net> (raw)
In-Reply-To: <4DFA6E23.6040700-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Hi Eric,
On Thu, 16 Jun 2011 15:57:07 -0500, Eric Sandeen wrote:
> https://bugzilla.redhat.com/show_bug.cgi?id=701735
>
> From the bug:
>
> > # 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)
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 majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2011-06-17 16:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-16 20:57 nilfs_cleanerd doesn't get started when /etc/mtab is a symlink Eric Sandeen
[not found] ` <4DFA6E23.6040700-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2011-06-17 16:08 ` Ryusuke Konishi [this message]
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=20110618.010858.91423049.ryusuke@osrg.net \
--to=konishi.ryusuke-zyj7fxus5i5l9jvzuh4aog@public.gmane.org \
--cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sandeen-H+wXaHxf7aLQT0dZR+AlfA@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