I saw a VMWare guest that hit a rare condition during boot; nfsdcld started too early to check access on /var/lib/nfs/nfsdcld which were still in read-only file system as follows: nfsdcld[...]: Unexpected error when checking access on /var/lib/nfs/nfsdcld: Read-only file system systemd[1]: nfsdcld.service: Main process exited, code=exited, status=226/NAMESPACE systemd[1]: nfsdcld.service: Failed with result 'exit-code'. nfsdcld.service needs to wait the root file system to be remounted at least. Signed-off-by: Seiichi Ikarashi <s.ikarashi@xxxxxxxxxxx> Reviewed-by: Jeff Layton <jlayton@xxxxxxxxxx> --- systemd/nfsdcld.service | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/systemd/nfsdcld.service b/systemd/nfsdcld.service index 3ced565..188123d 100644 --- a/systemd/nfsdcld.service +++ b/systemd/nfsdcld.service @@ -4,7 +4,7 @@ Documentation=man:nfsdcld(8) DefaultDependencies=no Conflicts=umount.target Requires=rpc_pipefs.target proc-fs-nfsd.mount -After=rpc_pipefs.target proc-fs-nfsd.mount +After=rpc_pipefs.target proc-fs-nfsd.mount systemd-remount-fs.service [Service] Type=forking
