From 2a5a1fda5cf2c3bdfd4baf67c4de6344a7febdc0 Mon Sep 17 00:00:00 2001 From: Thierry Vignaud Date: Fri, 14 Jan 2022 22:43:40 +0100 Subject: Use 'nolock' option for NFS Rationale: when building in iurt, it looks like we are missing some bits (due to missing deps?) and thus mounting fails because with: mount.nfs: rpc.statd is not running but is required for remote locking mount.nfs: Either use '-o nolock' to keep locks local, or start statd. mount.nfs: mounting 192.168.1.10:/mageia/unstable failed, reason given by server: No such file or directory --- mdk-stage1/NEWS | 2 ++ mdk-stage1/mount.c | 2 ++ 2 files changed, 4 insertions(+) (limited to 'mdk-stage1') diff --git a/mdk-stage1/NEWS b/mdk-stage1/NEWS index e8fae6eaf..d14c23cbd 100644 --- a/mdk-stage1/NEWS +++ b/mdk-stage1/NEWS @@ -1,3 +1,5 @@ +- use 'nolock' option for NFS + 2.58 - fix 'disk' method after kernel-5.15 breakage diff --git a/mdk-stage1/mount.c b/mdk-stage1/mount.c index eb52780fa..14b2b2fc2 100644 --- a/mdk-stage1/mount.c +++ b/mdk-stage1/mount.c @@ -91,6 +91,8 @@ int my_mount(char *dev, char *location, char *fs, int force_rw) } #ifndef DISABLE_MEDIAS + if (!strcmp(fs, "nfs")) + opts = "nolock"; if (!strcmp(fs, "vfat")) opts = "check=relaxed"; #endif -- cgit v1.2.1