https://bugzilla.novell.com/show_bug.cgi?id=397417
User nfbrown@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=397417#c3
Neil Brown changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
Info Provider| |olh@novell.com
--- Comment #3 from Neil Brown 2008-06-05 06:04:03 MDT ---
Remounting read-only seems an odd thing to do, but maybe there is a
good reason...
Yes, mount.nfs is doing the wrong thing here.
If you don't give it "-o nolock", it will try to see if statd is
running and complain if not. It might take a while to convince
itself that statd isn't running.
But it shouldn't do this test if "-o remount" is set as you cannot
change the "lock" flag with a remount.
There is a patch in nfs-utils that makes one change to the relevant
code. We can just change it with the following and it should
do the right thing.
Can you check?
++++++ nfs-utils-1.1.2-start-statd.patch ++++++
--- /var/tmp/diff_new_pack.h16245/_old 2008-06-05 14:02:47.000000000 +0200
+++ /var/tmp/diff_new_pack.h16245/_new 2008-06-05 14:02:47.000000000 +0200
@@ -57,7 +57,7 @@
goto out;
}
-+ if (!fake && lock) {
++ if (!fake && lock && ! (flags & MS_REMOUNT)) {
+ if (!start_statd()) {
+ nfs_error(_("%s: rpc.statd is not running but is "
+ "required for remote locking.\n"
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.