NFS Client mounts hang when exported directory do not exist
Subsystems (2)
PATCH 1/1 NFS Client mounts hang when exported directory do not exist
This patch fixes a regression that was introduced by the string based mounts.
nfs_mount() statically returns -EACCES for every error returned by the remote mounted. This is incorrect because -EACCES is an non-fatal error to the mount.nfs command. This error causes mount.nfs to retry the mount even in the case when the exported directory does not exist.
This patch maps the errors returned by the remote mountd into valid errno values, exactly how it was done pre-string based mounts. By returning the correct errno enables mount.nfs to do the right thing.
---
fs/nfs/mount_clnt.c renamed from fs/nfs/mount_clnt.c.orig +44 -1
@@ -21,6 +21,49 @@static struct rpc_program mnt_program; +static struct { +enum nfs_stat stat; +int errnum; +} mnt_errtbl[] = { + {NFS_OK ,0 }, + {NFSERR_PERM ,EPERM }, + {NFSERR_NOENT ,ENOENT }, + {NFSERR_IO ,EIO }, + {NFSERR_NXIO ,ENXIO }, + {NFSERR_ACCES ,EACCES }, + {NFSERR_EXIST ,EEXIST }, + {NFSERR_NODEV ,ENODEV }, + {NFSERR_NOTDIR ,ENOTDIR }, + {NFSERR_ISDIR ,EISDIR }, +#ifdef NFSERR_INVAL + {NFSERR_INVAL ,EINVAL },/* that Sun forgot */ +#endif + {NFSERR_FBIG ,EFBIG }, + {NFSERR_NOSPC ,ENOSPC }, + {NFSERR_ROFS ,EROFS }, + {NFSERR_NAMETOOLONG ,ENAMETOOLONG }, + {NFSERR_NOTEMPTY ,ENOTEMPTY }, + {NFSERR_DQUOT ,EDQUOT }, + {NFSERR_STALE ,ESTALE }, +#ifdef EWFLUSH + {NFSERR_WFLUSH ,EWFLUSH }, +#endif +/* Throw in some NFSv3 values for even more fun (HP returns these) */ + {71 ,EREMOTE }, +}; +static int mnt_errtbl_sz =sizeof (mnt_errtbl)/sizeof (mnt_errtbl[0 ]); + +static inline int mnt_err_map (int stat) +{ +int i; + +for (i =0 ; i < mnt_errtbl_sz; i++) { +if (mnt_errtbl[i].stat == stat) +return -mnt_errtbl[i].errnum; + } +return -EACCES ; +} +struct mnt_fhstatus {u32 status;struct nfs_fh *fh;
@@ -98,7 +141,7 @@ out_call_err: out_mnt_err:dprintk ("NFS: MNT server returned result %d\n" , result.status); - status = -EACCES ; + status =mnt_err_map (result.status); goto out; }
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 8 lines · Steve Dickson
This patch fixes a regression that was introduced by the string based mounts.
nfs_mount()statically returns-EACCESfor every error returned by the remote mounted. This is incorrect because-EACCESis an non-fatal error to the mount.nfs command. This error causes mount.nfs to retry the mount even in the case when the exported directory does not exist.
Quoted 4 lines
This patch maps the errors returned by the remote mountd into valid errno values, exactly how it was done pre-string based mounts. By returning the correct errno enables mount.nfs to do the right thing.
Does this mean the EACCES can/will again become fatal in mount.nfs like it used to be?
https://bugzilla.redhat.com/show_bug.cgi?id=439807
-Eric
A message that is not in the archive (sent off-list or not yet received): 1207927210.3379.1.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/[email protected]
Quoted 9 lines · Eric Paris
Quoted 8 lines · Steve Dickson
This patch fixes a regression that was introduced by the string based mounts.
nfs_mount()statically returns-EACCESfor every error returned by the remote mounted. This is incorrect because-EACCESis an non-fatal error to the mount.nfs command. This error causes mount.nfs to retry the mount even in the case when the exported directory does not exist.
Quoted 7 lines
Quoted 4 lines
This patch maps the errors returned by the remote mountd into valid errno values, exactly how it was done pre-string based mounts. By returning the correct errno enables mount.nfs to do the right thing.
Does this mean the EACCES can/will again become fatal in mount.nfs like it used to be?
EACCES is still a non-fatal error as it was... The problem is the kernel was should have been returning ENOENT, which is a fatal error, instead of EACCES.
steved.
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 11 lines · Steve Dickson
Quoted 9 lines · Eric Paris
Quoted 8 lines · Steve Dickson
This patch fixes a regression that was introduced by the string based mounts.
nfs_mount()statically returns-EACCESfor every error returned by the remote mounted. This is incorrect because-EACCESis an non-fatal error to the mount.nfs command. This error causes mount.nfs to retry the mount even in the case when the exported directory does not exist.
Quoted 8 lines
Quoted 7 lines
Quoted 4 lines
This patch maps the errors returned by the remote mountd into valid errno values, exactly how it was done pre-string based mounts. By returning the correct errno enables mount.nfs to do the right thing.
Does this mean the EACCES can/will again become fatal in mount.nfs like it used to be?
EACCES is still a non-fatal error as it was...
"non-fatal error as it was"? Huh? Back in the days of binary mount data it was fatal. Try this on a new and old system.
mount -o context=system_u:object_r:httpd_t:s0 server:/export /import
old system it was fatal and we died instantly with EACCES telling the user it was a permissions problem. New system I have to waste 2 minutes and then get a message about it timing out. It wasn't a timeout, it was a permission failure. Users are going to be looking down the wrong path..
Quoted 3 lines
The problem is the
kernel was should have been returning ENOENT, which is a fatal error, instead of EACCES.
That may well have been your problem, but it doesn't change the fact the EACCES has been a fatal error in mount.nfs until just recently. Why was it changed? When is EACCES not fatal?
-Eric
A message that is not in the archive (sent off-list or not yet received): 1207938902.3379.7.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/[email protected]
Quoted 4 lines · Eric Paris
Quoted 3 lines · Steve Dickson
Quoted 2 lines
Does this mean the EACCES can/will again become fatal in mount.nfs like it used to be?
EACCES is still a non-fatal error as it was...
I guess I didn't look back far enough...
Quoted 3 lines
"non-fatal error as it was"? Huh? Back in the days of binary mount data it was fatal. Try this on a new and old system.
Yes, I see...
Quoted 3 lines
That may well have been your problem, but it doesn't change the fact the EACCES has been a fatal error in mount.nfs until just recently. Why was it changed? When is EACCES not fatal?
It appears the change came in with the text-based mount.nfs changes
commit 4ce9ddfb03de06e90fb4cf0eb5767cb0e3a98905
Author: Chuck Lever <[email protected]> Date: Wed Oct 10 15:06:39 2007 -0400
text-based mount.nfs: sort between permanent and temporary errors
and I'm not sure why EACCES was deemed a non fatal error, but I'm beginning to agree with you... EACCES probably should be fatal... But thats something easily fixed in nfs-utils...
steved.
Quoted 7 lines · Steve Dickson
This patch fixes a regression that was introduced by the string based mounts.
nfs_mount()statically returns-EACCESfor every error returned by the remote mounted. This is incorrect because-EACCESis an non-fatal error to the mount.nfs command. This error causes mount.nfs to retry the mount even in the case when the exported directory does not exist.
I don't doubt this is the case, but I'd like to see a few real world examples (maybe even add them as documentary comments in mount.nfs or in the kernel).
Quoted 46 lines
This patch maps the errors returned by the remote mountd into
valid errno values, exactly how it was done pre-string based mounts. By returning the correct errno enables mount.nfs to do the right thing.Signed-off-by Steve Dickson <[email protected]>---
diff -up linux/fs/nfs/mount_clnt.c.orig
linux/fs/nfs/mount_clnt.cfs/nfs/mount_clnt.c renamed from fs/nfs/mount_clnt.c.orig +33
-0@@ -21,6 +21,49 @@static struct rpc_program mnt_program; +static struct { +enum nfs_stat stat; +int errnum; +} mnt_errtbl[] = { + {NFS_OK ,0 }, + {NFSERR_PERM ,EPERM }, + {NFSERR_NOENT ,ENOENT }, + {NFSERR_IO ,EIO }, + {NFSERR_NXIO ,ENXIO }, + {NFSERR_ACCES ,EACCES }, + {NFSERR_EXIST ,EEXIST }, + {NFSERR_NODEV ,ENODEV }, + {NFSERR_NOTDIR ,ENOTDIR }, + {NFSERR_ISDIR ,EISDIR }, +#ifdef NFSERR_INVAL + {NFSERR_INVAL ,EINVAL },/* that Sun forgot */ +#endif + {NFSERR_FBIG ,EFBIG }, + {NFSERR_NOSPC ,ENOSPC }, + {NFSERR_ROFS ,EROFS }, + {NFSERR_NAMETOOLONG ,ENAMETOOLONG }, + {NFSERR_NOTEMPTY ,ENOTEMPTY }, + {NFSERR_DQUOT ,EDQUOT }, + {NFSERR_STALE ,ESTALE }, +#ifdef EWFLUSH + {NFSERR_WFLUSH ,EWFLUSH }, +#endif +/* Throw in some NFSv3 values for even more fun (HP returns these) */ + {71 ,EREMOTE }, +}; +static int mnt_errtbl_sz =sizeof (mnt_errtbl)/sizeof (mnt_errtbl[0 ]); + +static inline int mnt_err_map (int stat)
fs/nfs/mount_clnt.c line 66
Quoted 10 lines
fs/nfs/mount_clnt.c renamed from fs/nfs/mount_clnt.c.orig +10
-0+{ +int i; + +for (i =0 ; i < mnt_errtbl_sz; i++) { +if (mnt_errtbl[i].stat == stat) +return -mnt_errtbl[i].errnum; + } +return -EACCES ; +} +
This probably isn't necessary. It looks like nfs_stat_to_errno() already does everything you want.
fs/nfs/mount_clnt.c out_call_err: · line 144
Quoted 9 lines
fs/nfs/mount_clnt.c renamed from fs/nfs/mount_clnt.c.orig +1
-1struct mnt_fhstatus {u32 status;struct nfs_fh *fh;@@ -98,7 +141,7 @@ out_call_err: out_mnt_err:dprintk ("NFS: MNT server returned result %d\n" , result.status); - status = -EACCES ; + status =mnt_err_map (result.status);
The question here is whether nfs_mount's other caller (NFSROOT) can handle error codes other than EACCES.
fs/nfs/mount_clnt.c out_call_err: · line 146
Quoted 2 lines
fs/nfs/mount_clnt.c renamed from fs/nfs/mount_clnt.c.orig +0
-0goto out; }
_______________________________________________
Fedora-kernel-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/fedora-kernel-list
Quoted 9 lines · Chuck Lever
Quoted 7 lines · Steve Dickson
This patch fixes a regression that was introduced by the string based mounts.
nfs_mount()statically returns-EACCESfor every error returned by the remote mounted. This is incorrect because-EACCESis an non-fatal error to the mount.nfs command. This error causes mount.nfs to retry the mount even in the case when the exported directory does not exist.
Quoted 3 lines
I don't doubt this is the case, but I'd like to see a few real world examples (maybe even add them as documentary comments in mount.nfs or in the kernel).
Thats easy.. Do a Fedora install over NFS and mistype the mount point. Instead of returning immediately like it should, one has to wait 2mins for the error..
ENOENT during a mount has always been a fatal error as it should be and this patch is just restoring that fact.
steved.